Disable All Advertising
Image
EAN-139781841763637   EAN-13 barcode 9781841763637
Product NameKriegsmarine U-boats 1939–45 (1) (New Vanguard) (v. 1)
CategoryBook / Magazine / Publication
Short DescriptionHeight:9.76 inches / Length:7.24 inches / Weight:0.4 pounds / Width:0.2 inches
Amazon.comA Buy on Amazon ~ 1841763632
SKUACOMMP2_BOOK_USEDLIKENEW_1841763632
Price New15.95 US Dollars    (curriencies)
Price Used7.01 US Dollars    (curriencies)
Width2.54 inches    (convert)
Height245.36 inches    (convert)
Length7.21 inches    (convert)
Weight6.24 ounces    (convert)
AuthorGordon Williamson
Page Count48
BindingPaperback
Published05/25/2002
Long DescriptionThis, the first of two volumes on Germany's World War II U-boats, traces their development from the early U-boats of the Kaiser's Navy, the prohibition on Germany having U-boats following the Armistice in 1918 and the subsequent Treaty of Versailles, the secret development of U-boats using a 'cover-firm' in Holland, culminating in the formation of the 1st U-boat Flotilla in 1935 with the modern Type II. The operational history section includes examples from the Classes Type VIIA, Type VIIB, VIID, VIIE and VIIF before concentrating on the mainstay of the U-boat arm, the Type VIIC. Comparisons are also made with the standard allied submarines, their strengths, weaknesses and U-boat tactics.
Similar Items9781904687962: Kriegsmarine U-Boats: 1939 - 1945 (The Essential Submarine Identification Guide)
9780548181218: Kriegsmarine U-Boats: 1939 - 1945 (The Essential Submarine Identification Guide)
9781163268957: Imperial Japanese Navy Submarines 1941-45 (New Vanguard)
9781841768724: Wolf Pack: The Story Of The U-Boat In World War Ii (General Military)
9781841763620: U-Boats Of The Kaiser's Navy (New Vanguard)
9780764307874: German U-Boat Type XXI: (Schiffer Military/Aviation History) (Schiffer Military History)
9781846030901: Imperial Japanese Navy Submarines 1941–45 (New Vanguard)
9781841768595: US Submarines 1941–45 (New Vanguard)
9781161622102: Kriegsmarine U-Boats: 1939 - 1945 (The Essential Submarine Identification Guide)
9781841763644: Kriegsmarine U-boats 1939–45 (2) (New Vanguard)
View 19 more similar items
Created02-26-2012 8:25:03pm
Modified09-22-2017 10:57:05am
MD5dda210a7969631d4cd59957bef2c6eb8
SHA256f427613cd519e487d7e10edd5832460cdb1629a36f2e2ec6768a759203bc6a99
Search Googleby EAN or by Title
Query Time0.0263429

An article of interest

Making use of the tools we offer

Data Feed API v3 - Access and Data Layout

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.