Image
EAN-139780786028061   EAN-13 barcode 9780786028061
Product NameTexas Bloodshed (Sidewinders)
CategoryBook / Magazine / Publication
Amazon.comA Buy on Amazon ~ 0786028068
SKUB9780786028061
Price New1.14 US Dollars    (curriencies)
Price Used0.01 US Dollars    (curriencies)
Width0.89 inches    (convert)
Height6.78 inches    (convert)
Length4.12 inches    (convert)
AuthorWilliam W. Johnstone, J.A. Johnstone
Page Count360
BindingMass Market Paperback
Published06/01/2012
Long DescriptionThe Greatest Western Writer Of The 21st Century

With his monumental Mountain Man and Eagles series, William W. Johnstone has become America's most popular Western writer. Now, with J.A. Johnstone, he unleashes the Sidewinders, two honest Texas cowboys with an uncanny knack for lighting wildfires everywhere they go. . .

Home Sweet Deadly Home

If there's anything better than coming home to Texas, it's getting paid to do it. For Scratch Morton and Bo Creel, always on the hunt for funds, the job is taking three vicious criminals from Arkansas to Tyler, Texas for trial. Little do they know that one of the criminals, the one that's a beautiful woman, is the most dangerous of all. Soon the journey home turns into a race for buried treasure, a shoot-out, and another double cross--until Scratch and Bo are making one last mad, bullet-sprayed dash through the land of their birth. . . or the land of their death. . .
Similar Items9780786019229: Massacre at Whiskey Flats (Sidewinders, Book 2)
9780786031207: The Butcher of Bear Creek (Sidewinders)
9780786028795: Cutthroat Canyon (Sidewinders)
9780786023479: Deadwood Gulch (Sidewinders, No. 5)
9780786021239: Mankiller, Colorado (Sidewinders, No. 4)
9780786019212: Sidewinders
Created11-22-2012 3:40:28pm
Modified10-09-2017 1:23:43pm
MD5aa35b404a4fc70acf6a236e2e6cb101d
SHA25676c9f8b034cd7225823cb546ff6fbf2c16e90091cff3a4e6aad80f38ae335d28
Search Googleby EAN or by Title
Query Time0.0174689

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...

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

Close

Dialog