Image
EAN-139780786026173   EAN-13 barcode 9780786026173
Product NameThe Loner: Killer Poker
CategoryBook / Magazine / Publication
Amazon.comA Buy on Amazon ~ 0786026170
SKUMON0000043184
Price New24.33 US Dollars    (curriencies)
Price Used0.01 US Dollars    (curriencies)
Width0.94 inches    (convert)
Height6.86 inches    (convert)
Length4.26 inches    (convert)
AuthorJ.A. Johnstone
Page Count320
BindingMass Market Paperback
Published04/01/2011
FeaturesUsed Book in Good Condition
Long DescriptionHe came West in search of the truth. Out here, the truth is more than enough to get you killed. . . Hunter And The Hunted Conrad Browning had money, a manservant and a mission: to find his missing children and meet them for the first time. He's come as far as Denver, dodged a bullet from a beautiful assassin, and landed in a big buy-in poker tournament against a ruthless heavy-betting cattle baron with a plan of his own--to take this city slicker into the wilderness, and hunt him like an animal. But Rance McKinney doesn't know who he is facing. The son of legendary gunman Frank Morgan, Conrad goes by the moniker of the Loner. Now it's the Loner against McKinney, the hunter and the hunted. And when he's cornered, the Loner is the most dangerous beast of all. . .
Similar Items9780786028535: Bullets Don't Die (Loner, Book 13) (The Loner)
9780786028528: The Loner: Hard Luck Money
9780786028511: Brutal Vengeance (The Loner)
9780786028504: Inferno (The Loner)
9780786028160: The Loner Book 1
9780786027682: The Loner: The Bounty Killers
9780786026197: Crossfire (The Loner)
9780786026180: The Blood of Renegades (The Loner)
9780786026166: Trail of Blood (The Loner)
9780786021536: The Loner: Dead Man's Gold
9780786021529: The Loner: The Devil's Badland
Created11-22-2012 3:38:41pm
Modified05-01-2020 1:30:42am
MD529a3320327827c46cb3956cf46783a1a
SHA256088ddb9e1e102bba24f9f264ef08540c48cb0701c15f1505a79fac636a3fc30f
Search Googleby EAN or by Title
Query Time0.0169160

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