Image
EAN-139780811710794   EAN-13 barcode 9780811710794
Product NamePanzer Warfare On The Eastern Front
LanguageEnglish
CategoryBook / Magazine / Publication
Short DescriptionHeight:9.02 inches / Length:5.98 inches / Weight:1.12 pounds / Width:1.14 inches
Amazon.comA Buy on Amazon ~ 0811710793
SKUING0811710793
Price New15.73 US Dollars    (curriencies)
Price Used5.94 US Dollars    (curriencies)
Width1.13 inches    (convert)
Height9 inches    (convert)
Length6 inches    (convert)
Weight17.92 ounces    (convert)
AuthorHans Schaufler
Page Count352
BindingHardcover
Published05/01/2012
Long DescriptionVivid narrative of tank combat on the brutal Eastern Front during World War IIDescribes clashes between German Tigers and Soviet T-34sCovers the German invasion of the Soviet Union in 1941, Stalingrad, Kursk, and moreContains numerous firsthand accounts
Similar Items9780811711708: Armored Bears: The German 3rd Panzer Division in World War II (Volume 1)
9781849085526: Demyansk 1942–43: The frozen fortress (Campaign)
9780811710862: The Combat History of the 23rd Panzer Division in World War II
9780691008530: Soldiers Of Destruction
9780263760705: Your Loyal And Loving Son: The Letters Of Tank Gunner Karl Fuchs, 1937-1941
9780811706568: Panzergrenadier Aces: German Mechanized Infantrymen In World War Ii (The Stackpole Military History Series)
9781874622581: Once I Had A Comrade: Karl Roth And The Combat History Of The 36th Panzer Regiment 1939-45
9781841761411: The Military Sniper Since 1914 (Elite)
9789623616454: Waffen Ss In Combat (Warrior)
9781572491793: Condemned To Live: A Panzer Artilleryman's Five-Front War
View 29 more similar items
Created11-22-2012 4:04:59am
Modified10-08-2017 6:06:21pm
MD568f3106786ea9a8a38b2b77d8abfba23
SHA2562ff92a31847ee3210b86b863967b78b2c15e51ecfb0d1b127b632494b92f88d7
Search Googleby EAN or by Title
Query Time0.0179121

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