EAN-139780739319550   EAN-13 barcode 9780739319550
Product NameDouble Cross Blind
LanguageEnglish
CategoryBook / Magazine / Publication
Short DescriptionRandom House Audio
Amazon.comA Buy on Amazon ~ 0739319558
Long DescriptionDecember 1, 1941 It is seven days before the Japanese attack Pearl Harbor. Days that are numbered for Sondegger, a Nazi spy captured in London while on a mission to take down the Twenty Committee, a German network of spies the British have turned. For American Tom Wall, the days have run together as he awakens to find himself locked in a British military asylum. Wounded and shell-shocked, all he knows is that his brother, Earl, betrayed his unit in Crete, causing one of the bloodiest massacres of the war. MI5 releases Tom by way of a bargain. Pretend to be Earl and convince Sondegger to reveal how and where he has arranged to transmit his intelligence to Germany. Fail, and spend the rest of the war in jail. Succeed, and Tom, though still considered a danger to himself, will be allowed to leave the hospital to find Earl—who may well be a Nazi informant. But Sondegger proves himself to be a formidable opponent. Even as he surrendered himself to the British, he knew the Japanese fleet had sailed for Pearl Harbor. The question is: Who will gain more if the Allies prevent the attack? Sondegger, MI5, the OSS, Tom, and Earl’s wife, Harriet, all have different answers. Unable to trust anyone, Tom attempts to save the Twenty Committee and stop the attack on Pearl Harbor as the clock counts down. In his electrifying debut, Joel Ross combines political insights with the high stakes and fast pace of classic espionage fiction, and he delivers what others have not in more than a decade—a Nazi spy novel that you cannot put down.
Created11-14-2012 6:25:17pm
Modified05-01-2020 12:13:48am
MD506dc31f5180bc2b019bd640e28c3475f
SHA2565dd0837404b3a9c78957a18245d95733897c9d85351e8bda97ee8bea5b858e21
Search Googleby EAN or by Title
Query Time0.0333500

Article of interest

This describes how to use version 3.x of the data feed. Version 2.x of the feed is still supported. Version 1.x of the feed is no longer supported in any way.

IMPORTANT: Starting with version 3.2, we have a new property and a new way of dealing with product images. Read about it here.

Accessing the data requires your account to have an active data feed. This switch can be turned on or off on the data feed page. This is also where you will be able to view your KEYCODE which is required to make calls to the feed.

Main changes from version 2.x to 3.x include (but not limited to)...

Calls to the data feed are made via HTTP GET or HTTP POST requests. There are only a few required parameters when making a call.

Most other parameters are optional and they will alter the way data is returned to you and how your request is processed. You can also pass in your own values that you need carried through. Any parameter that the system doesn't recognize will be returned AS-IS in the status block. This can be handy in situations where you are pulling the data in an asyncronus manor and need extra information passed into your callback routine.

When performing a lookup...

When updating data...

When deleting data...

There are some special "get" operations that need no other parameters. You would not use "find" or "update" when using these. Only use the "keycode", "mode" and "get" for these items. These operations are important because many of our elements are data driven and that data changes over time. We normally don't remove attributes or categories but we do often add to the collection.

The returned data can come back in JSON or XML format. In either case the structure of the data is the same. Because it is easier to read, we will be using XML to demonstrate the layout of the result. Here is the data layout. Notice that this is a complex object and some elements have child elements and some elements may be arrays with repeating content.

The easiest way to get the feel of the data is to make several requests using your web browser and ask for the data in XML format. Although JSON is often easier to work with in code, the XML output is often easier for people to read because of the nice markup tags that wrap around each element and the web browser will usually do a nice job of indenting to make it clear which elements are stored within other elements.

Close

Search

Close

Share