Disable All Advertising
Image
EAN-139780060188603   EAN-13 barcode 9780060188603
Product NameDevil At My Heels: A Ww Ii Hero's Epic Saga Of Torment, Survival, And Forgiveness
LanguageEnglish
CategoryBook / Magazine / Publication
Short DescriptionHardcover
Amazon.comA Buy on Amazon ~ 006018860X
SKU8-J-1-00341
Price New27.35 US Dollars    (curriencies)
Price Used6.00 US Dollars    (curriencies)
Width1.01 inches    (convert)
Height9 inches    (convert)
Length6 inches    (convert)
Weight20.8 ounces    (convert)
AuthorLouis Zamperini, David Rensin
Page Count292
BindingHardcover
Published01/21/2003
Long DescriptionThe bestselling autobiography of the legendary Louis Zamperini, hero of the blockbuster Unbroken A modern classic by an American legend, Devil at My Heels  is the riveting and deeply personal memoir by U.S. Olympian, World War II bombardier, and POW survivor Louis Zamperini. His inspiring story of courage, resilience, and faith has captivated readers and audiences of  Unbroken,  now a major motion picture directed by Angelina Jolie. In  Devil at My Heels , his official autobiography (co-written with longtime collaborator David Rensin), Zamperini shares his own first-hand account of extraordinary journey—hailed as “one of the most incredible American lives of the past century” ( People ). A youthful troublemaker, a world-class NCAA miler, a 1936 Olympian, a WWII bombardier: Louis Zamperini had a fuller life than most. But on May 27, 1943, it all changed in an instant when his B-24 crashed into the Pacific Ocean, leaving Louis and two other survivors drifting on a raft for forty-seven days and two thousand miles, waiting in vain to be rescued. And the worst was yet to come when they finally reached land, only to be captured by the Japanese. Louis spent the next two years as a prisoner of war—tortured and humiliated, routinely beaten, starved and forced into slave labor—while the Army Air Corps declared him dead and sent official condolences to his family. On his return home, memories of the war haunted him nearly destroyed his marriage until a spiritual rebirth transformed him and led him to dedicate the rest of his long and happy life to helping at-risk youth. Told in Zamperini’s own voice,  Devil at My Heels  is an unforgettable memoir from one of the greatest of the “Greatest Generation,” a living document about the brutality of war, the tenacity of the human spirit, and the power of faith.
Similar Items9780226257136: A Higher Call: An Incredible True Story of Combat and Chivalry in the War-Torn Skies of World War II
9780224619103: A Higher Call: An Incredible True Story of Combat and Chivalry in the War-Torn Skies of World War II
9780195210514: A Higher Call: An Incredible True Story of Combat and Chivalry in the War-Torn Skies of World War II
9780070125490: A Higher Call: An Incredible True Story of Combat and Chivalry in the War-Torn Skies of World War II
9780061345050: A Higher Call: An Incredible True Story of Combat and Chivalry in the War-Torn Skies of World War II
9780060126926: A Higher Call: An Incredible True Story of Combat and Chivalry in the War-Torn Skies of World War II
9780002240802: A Higher Call: An Incredible True Story of Combat and Chivalry in the War-Torn Skies of World War II
9780002008457: A Higher Call: An Incredible True Story of Combat and Chivalry in the War-Torn Skies of World War II
9780306822377: Brothers Forever: The Enduring Bond Between A Marine And A Navy Seal That Transcended Their Ultimate Sacrifice
9780062368331: Don't Give Up, Don't Give In: Lessons From An Extraordinary Life
View 181 more similar items
Created06-01-2012 1:05:00am
Modified04-30-2020 2:56:53pm
MD55357a11573fc15afa183ab00a541ead9
SHA25633ee7535d79dbb025fff1555971b583cf44843a898491ba4b6975df30d75ca54
Search Googleby EAN or by Title
Query Time0.0333049

An article of interest

Making use of the tools we offer

Creating your own UPC / EAN application

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.