Disable All Advertising
Image
EAN-139780747598596   EAN-13 barcode 9780747598596
Product NameLegacy Of Blood: Spartan 3
CategoryBook / Magazine / Publication
Short DescriptionPaperback
Amazon.comA Buy on Amazon ~ 0747598592
SKUYV-9780747598596
Price New5.35 US Dollars    (curriencies)
Price Used0.01 US Dollars    (curriencies)
Width0.79 inches    (convert)
Height7.8 inches    (convert)
Length5.08 inches    (convert)
Weight7.52 ounces    (convert)
AuthorMichael Ford
Page Count304
BindingPaperback
Published01/05/2009
FeaturesUsed Book in Good Condition
Long DescriptionAfter victory against the Persians, Lysander and the other young warriors from the Spartan barracks are in desperate need of a rest from battle. But a messenger has brought news that Taras, a distant outpost of the Spartan empire, is under siege. The citizens of Taras have organised an uprising and Sparta is in danger of losing a vital trading port. Lysander and the other boys set sail immediately for southern Italy. They quickly discover that the men of Taras are far more organised than they thought, and will not be easily beaten. In the heat of battle Lysander finds himself in front of the great statue in the main square. The figure is wearing the Fire of Ares - he must be Lysander's ancestor. Shocked, he knows that he must find out his connection to this town and its people, and in so doing uncover a little more of his mysterious heritage, hidden from him for so long.
Similar Items9780802797940: Birth of a Warrior (Spartan Quest)
9780747593874: Birth Of A Warrior: Spartan 2
9780747593669: The Fire of Ares: Spartan 1
9780802798275: The Fire Of Ares (Spartan Quest)
Created11-16-2012 5:25:00pm
Modified09-16-2017 12:54:10pm
MD5a60b8acd00db6bc1280a1f69a290a06a
SHA256cd61d8fea564c2d489d5ce885a53bf42725a07461d46ccf99e6ef5bbfaba1921
Search Googleby EAN or by Title
Query Time0.0120711

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