Disable All Advertising
EAN-130025192122026   EAN-13 barcode 0025192122026
UPC-A025192122026   UPC-A barcode 025192122026
Product NameMidway (Collector's Edition)
CategoryElectronics / Photography: A/V Media: Movie / TV
Short DescriptionDVD
Amazon.comA Buy on Amazon ~ B00005N5S3
Price New9.48 US Dollars    (curriencies)
Price Used14.00 US Dollars    (curriencies)
Weight4 ounces    (convert)
Long DescriptionCracking a Japanese code leads Adm. Nimitz and Navy officers to Yamamoto's fleet in the Battle of Midway, June 1942
Similar Items9780933126299: Destination Tokyo: A Pictorial History Of Doolittle's Tokyo Raid, April 18, 1942
9780929521527: Destination Tokyo: A Pictorial History of Doolittle's Tokyo Raid, April 18, 1942
9780792844013: Force 10 From Navarone
9780792841678: Run Silent, Run Deep
9780792841654: Bataan
9780792839736: A Bridge Too Far
9780792299912: National Geographic's The Battle for Midway
9780792288152: Search for Kennedy's Pt 109
9780792232087: Lost Fleet of Guadalcanal
9780792187158: Hunt for Red October
9780790793184: Battleground
9780790765242: Battle of the Bulge
9780790741819: The Big Red One
9780788832826: National Geographic - Beyond the Movie - Pearl Harbor
9780782010046: Sands of Iwo Jima
9780780632776: Gettysburg
9780767868303: Anzio
9780767858731: The Bridge on the River Kwai (Limited Edition)
9780767821780: The Guns of Navarone
9780671770075: Incredible Victory
8712626016007: The Longest Day
7321900651561: Kelly's Heroes
5051892009379: humphrey bogart collection (6 Dvd) Italian Import
5050582979442: Sands of Iwo Jima [DVD]
5050070022667: Battle of Britain
5050070020564: A Bridge Too Far
5050070020243: Battle of Britain (Special Edition) [Region 2]
5039036030717: Battle Of Britain Definitive Edition [Import anglais]
5039036024624: Guadalcanal Diary, The - Studio Classics [Import anglais]
5039036012096: Desert Rats
5039036012089: The Enemy Below
5014437835536: The Hunt for Red October
3257980513687: A la poursuite d'Octobre Rouge [Import belge]
0887090089302: Pork Chop Hill
0885444724466: The Battle of Midway: WWII in Color
0883929579488: Kelly's Heroes
0097363202073: Hunt for Red October
0097361244846: In Harm's Way / Donovan's Reef
0054961981090: Day One
0032429281555: In Harm's Way
0026359920523: Band Of Brothers
0024543987673: Von Ryan's Express / Tora Tora Tora / Twelve O'clock High / The Blue Max Quad Feature
0024543029984: Longest Day
0024543029977: Longest Day
0024543013174: Tora! Tora! Tora!
0018713811295: World War II - Greatest Battles: The Normandy Invasion/The Victory
0012569798625: They Were Expendable
0012569698925: Never So Few
0012569515628: Kelly's Heroes
0011891983525: George C. Scott The Last Days of Patton
0011891702089: Bridge at Remagen/Devil's Brigade/633 Squadron
0011301628633: Color Documentaries of WWII
0002454323469: Patton
Modified10-10-2017 2:17:47am
Search Googleby EAN or by Title
Query Time0.0944769

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.