EAN-139780192801401   EAN-13 barcode 9780192801401
Product NamePostwar: A History Of Europe Since 1945
CategoryBook / Magazine / Publication
Short DescriptionPaperback
Amazon.comA Buy on Amazon ~ 0143037757
Price New4.93 US Dollars    (curriencies)
Price Used4.90 US Dollars    (curriencies)
Width1.75 inches    (convert)
Height9.09 inches    (convert)
Length6.07 inches    (convert)
Weight32.8 ounces    (convert)
AuthorTony Judt
Page Count960
FeaturesPenguin Books
Long DescriptionBeginning on August 4, 1914, the day Britain entered the "Great War," this book guides us through three decades of unparalleled upheaval and change in Britain that eventually lead to the defeat of Japan in 1945--a momentous event that marked the end of the Second World War. Twin themes of international conflict and mass unemployment in England predominate. And besides a full account of foreign and domestic politics that were enacted to deal with them, Taylor pays particular attention to the impact of events on everyday lives. It is an essential work from one of the finest historians of the twentieth century--a book that no one interested in British affairs will want to be without.
Similar Items9780140051377: The Invention Of Decolonization: The Algerian War And The Remaking Of France
9780140041156: Dark Continent: Europe's Twentieth Century
9780091604400: The Lost Children: Reconstructing Europe's Families After World War Ii
9780073348506: The Dynamics Of Mass Communication: Media In The Digital Age With Media World 2.0 Dvd-Rom
9780070692282: From The Soviet Bloc To The European Union: The Economic And Social Transformation Of Central And Eastern Europe Since 1973
9780060540364: Germany 1945: From War To Peace
9780043270325: Europe: A History
9780027365559: The Lost Children: Reconstructing Europe's Families After World War Ii
9780006154167: Europe: A History
8601400944400: Ill Fares The Land
View 59 more similar items
Created03-17-2012 1:05:00am
Modified10-08-2017 2:50:46pm
Search Googleby EAN or by Title
Query Time0.0202370

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.