Image
EAN-139781891118432   EAN-13 barcode 9781891118432
Product NameThe Legacy Of The Dc-3
LanguageEnglish
CategoryBook / Magazine / Publication
Amazon.comA Buy on Amazon ~ 1891118439
SKU1006-WS0701-A04010-1891118439
Price New28.50 US Dollars    (curriencies)
Price Used24.50 US Dollars    (curriencies)
AuthorHenry M Holden
Page Count365
BindingPaperback
Published04/21/2017
Long DescriptionWith a Foreword by Donald W. Douglas, Jr., this book is the most comprehensive and interesting book ever written about the DC-3, the most widely-beloved airplane of all time. Legacy of the DC-3 contains dozens of never-before published photos and anecdotes about the airplane that changed the world. It has the most complete history of the development of the DC-3/C-47 ever published. With over 200 histories of specific DC-3 aircraft, The Legacy of the DC-3 combines the personalities behind its development, the struggles that shaped this great airplane, and a chronological history of its peacetime and wartime adventures. It includes detailed accounts of DC-3s flying themselves, to monkeys in the cockpit, mail, freight and even other aircraft. The accounts go on. The Gooney Bird, its affectionate wartime sobriquet, was meant to fly, and fly she did - over 100 billion miles with over 700 million passengers. The author has carefully researched (and annotated) a masterpiece, including a roster of every surviving DC-3/C-47 in the United States he could locate, as well as 22 appendices, with one of these including details on all 43 variants produced. The appendices alone are worth the purchase of the book. There has never been another volume on the DC-3 that has accomplished so much, and in a style that all readers can enjoy. The Legacy of the DC-3 brings people and historical perspectives together to provide fascinating reading. You may have other DC-3 books on your shelf, but you need this one to get the full story. 365 pages, softbound, 8½ x 11 with about 500 photographs and illustrations
Similar Items9780830681945: The Dc-3: 50 Years Of Legendary Flight
9780879385439: Dc-3 And C-47 Gooney Birds: Includes The Dc-2, Dc-3, C-47, B-18 Bolo, B-23 Dragon, The Basler Turboprop Goonies, And Many More
9780760342916: Douglas DC-3 Dakota Owners' Workshop Manual: An insight into owning, flying, and maintaining the revolutionary American transport aircraft
9780874743586: Dc-3: A Legend In Her Time: A 75th Anniversary Photographic Tribute
9780615228778: Dc-3: A Legend In Her Time: A 75th Anniversary Photographic Tribute
9780764300646: The Amazing Gooney Bird: The Saga Of The Legendary Dc-3/C-47
Created10-06-2012 10:05:48am
Modified04-21-2017 7:18:18pm
MD58ed38bb30a296abb353ac13561fdaac3
SHA25685aaced0a3db23585b891f42c851de8b721b4cf7f4686343304fdd6810a4d798
Search Googleby EAN or by Title
Query Time0.0282559

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