Image
EAN-130888574099244   EAN-13 barcode 0888574099244
UPC-A888574099244   UPC-A barcode 888574099244
Product NameHer Alibi
CategoryElectronics / Photography: A/V Media: Movie / TV
Amazon.comA Buy on Amazon ~ B00X3DC8IS
ModelB00X3DC8IS
Price New11.66 US Dollars    (curriencies)
Price Used9.19 US Dollars    (curriencies)
RatingPG - Parental Guidance Suggested
IMDbIMDb Link
Run Time94 minutes
CastHurd Hatfield, James Farentino, Paulina Porizkova, Tom Selleck, William Daniels
Run Time94 minutes
Width5.5 inches    (convert)
Height0.5 inches    (convert)
Length7.5 inches    (convert)
Weight22 hundredths pounds    (convert)
BindingDvd
FormatNTSC
Published05/19/2015
Run Time94 minutes
Long DescriptionA mild-mannered mystery novelist lives vicariously through the adventures of his fictional hero, a dashing detective. When a foreign beauty, accused of murder, crosses his path, he supplies her with an alibi -- only to begin a series of near-fatal accidents. When sold by Amazon.com, this product will be manufactured on demand using DVD-R recordable media. Amazon.com's standard return policy will apply.
Similar Items9780767828154: Runaway
0883316654606: Broken Trust
0786936758337: Three Men and a Baby/Three Men and a Little Lady
0759731710329: High Road to China
0759731413725: High Road to China
0689721853524: High Road to China
0053939834925: Running Mates
0043396046993: Runaway
0027616865816: Quigley Down Under
0025192353826: Mr. Baseball
0012569721807: Louis L'Amour's The Sacketts
0011301690333: Gypsy Warriors
Created04-14-2018 2:32:48am
Modified04-30-2020 9:22:18am
MD5aa6ad06d89ad013b58be3d72b72ab8a8
SHA25635e1035b122d1b5802bf1fb8787655cfcfd6afc5934e0ac8e865016b2ef69473
Search Googleby EAN or by Title
Query Time0.0238159

Article of interest

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