Image
EAN-130031398278726   EAN-13 barcode 0031398278726
UPC-A031398278726   UPC-A barcode 031398278726
Product NameSource Code
CategoryElectronics / Photography: A/V Media: Movie
Web Link
Amazon.comA Buy on Amazon ~ B079ZSVP6F
ModelB079ZSVP6F
Price New13.99 US Dollars    (curriencies)
Price Used8.90 US Dollars    (curriencies)
RatingPG-13 - Parents Strongly Cautioned
IMDbIMDb Link
TrailerWatch The Trailer
Run Time93 minutes
CastJake Gyllenhaal, Michelle Monaghan, Vera Farmiga, Jeffrey Wright
DirectorDuncan Jones
GenreMYSTERY,ROMANCE,SCI-FI
Run Time112 minutes
Width5.39 inches    (convert)
Height0.51 inches    (convert)
Length6.77 inches    (convert)
Weight21 hundredths pounds    (convert)
BindingBlu-ray
Release Year2011
Format4K
Run Time112 minutes
Long DescriptionArmy Captain Colter Stevens finds himself working on a special program where his consciousness can be inserted into another human being. The only catch is can only be there for 8 minutes at any given time. That morning, a bomb exploded on a commuter train just outside Chicago. He occupies the body of teacher going to work on that train and is confused as to what he is doing or why he is there as his last memory is of flying his helicopter on a combat mission in Afghanistan. Those in charge of the program explain to him that there is a bomb on the train, and that he must locate it. More importantly, he must identify the bomber as another bombing is expected later that day. He is also told however that he cannot change the past and can only gather information. As he develops a liking for his traveling companion Christina, he sets out to test that theory.
Similar Items0031398285175: Knowing 4K Ultra HD
0031398285168: Push 4K Ultra HD
0031398250562: Now You See Me 2
0031398119289: Brothers
0025192224232: Escape Plan
0025192098369: Red
0025192093265: Red
0024543759430: Limitless
0024543475798: Die Hard 30th Anniversary
0013132636443: Snowpiercer
View 11 more similar items
Created06-14-2018 12:01:08am
Modified06-05-2019 4:38:26pm
MD577e22ed5f69a7a045d0e52ae0147289a
SHA25687a793417710f952b39dd92918d58580c6d643bcf4f2b8cbefad6fd5e6d139ec
Search Googleby EAN or by Title
Query Time0.0034990

You may have a need for your application to work with our databse. There are many steps in creating an application and the needs of each application can be very different. But the basic data movement contept is pretty much the same in every case.

First of all, your application shouldn't rely on our server. This might seem like a quick way to get your application up and running with little cost but in the end, your app will suffer because it will have to share computing time with every other app that is trying to access our data and network bandwidth. And if we change the way our data is delivered, you would have to re-deploy new copies of your app to every machine.

You should always have your application communicate with your own server. This way you control the format of the communication between your app and the data. And if we need to change our data format, you only need to make the change in the module between your server and our server. Your users running your app won't see any impact or loss of service while changes are made to the communication between your server and our server.

Application Data Diagram

This diagram demonstrates the basic data flow concept. Each device running your application would make requests (red) for data against your server. Your server would talk do your own database to find the needed information and return that information to the requesting devices. When you don't have the data in your database, your server makes a connection to our server requesting the needed information. Our server performs a lookup in our database and if we have the data we return it to your server.

Once you receive the data from our server, you need to store a copy in your database for the next time it is needed by your users. You also need to return the data to the requesting devices just as you would if you found the data in your database in the first place. Except for a slight delay in getting the data, your user shouldn't see any difference beween getting the data directly from your database or getting it from our database.

The odds are, if one user requests a peice of information from your server, another user will request that same information soon after. This is why you need to keep a copy of the data once you query it from our database. You don't want every user to encounter a delay when requesting the same bit of information.

If you are creating your application and database from scratch, there are a few ways to get started. The basic concept that we suggest is the lowest cost and most effective method that we have seen so far. Here are the basic steps you should follow...

 

  1. Create your own database with the information you want to track (few records are needed)
  2. Create your server aplication to control data flow on your system
  3. Create the interface between your server and ours using the data feed process. This can be done for FREE while you are developing. Once you go into production you MAY need to pay a fee to maintain fast data access. But if you feed data back to us you may be able to continue using the free feed. It depends on your actual need.
  4. Build your user application. This can be a phone app or something that is run from computers. Your user app is completly in your control and will talk to your server not ours.
  5. Test your app well. Make sure that when your server can't find the data in your database that it communicates with ours to get the answer.
  6. When your basic testing is done, you should load your database with an initial data load. You can get this data from our download page for a reasonable fee.
  7. Test some more!
  8. Release your app to the world and watch it go.

Althought the details involved in building your application and server and database are going to be different than what others might see, the basic concepts and steps will be similar as outlined here.

We have seen several app developers follow these basic steps with great success. We have also seen a few app developers try to take short cuts only to see their apps fail or strugle.

The key to a successful app is performance and easy maintenance. By creating your own server and keeping your own database you will have control over those aspects. It is much easier to set your application and communication structure up correctly from the start than it is to go back and rebuild it later.

Hopefully, this outline has been of value to you. Take some time to look around the rest of our site, check out our sample data and the data feed pages. Look at our statistics page. And if you still have questions, you are always welcome to ask.

 

Close

Search

Close

Share

Close

Dialog