Disable All Advertising
Image
EAN-139780486412368   EAN-13 barcode 9780486412368
Product NameA History Of Playing Cards And A Bibliography Of Cards And Gaming
LanguageEnglish
CategoryBook / Magazine / Publication
Short DescriptionPaperback
Amazon.comA Buy on Amazon ~ 0486412369
Price New13.65 US Dollars    (curriencies)
Price Used10.00 US Dollars    (curriencies)
Width1.2 inches    (convert)
Height9.1 inches    (convert)
Length6.1 inches    (convert)
Weight30.72 ounces    (convert)
AuthorCatherine Perry Hargrave
Page Count512
BindingPaperback
Published06/13/2012
Long DescriptionMost likely invented in the Far East, playing cards arrived in Europe at roughly the same time as paper money and gunpowder, and by the early eleventh century were in widespread use in France. This classic history, never superseded, not only tells the story of playing cards and their manufacture, but also provides the reader with a fascinating overview of heraldry, geography, history, and social and political activities over the past six centuries. In addition to making extensive use of the magnificent collection of the United States Playing Card Company in Cincinnati, this volume focuses on playing cards of China, Japan, India, Europe, Russia, and America. Also included is an enormous annotated bibliography of more than 900 items on playing cards and games, and probably the largest range of card illustrations, all royalty-free, ever assembled in one place: 1,462 photographs, of which 16 are in color on the covers.
Similar Items9782080111340: Collectible Playing Cards (Collectibles)
9781572813106: American Playing Cards Supplement And Price Guide, Second Edition
9780718824082: Playing Cards Of The World: A Collector's Guide
9780706400496: Playing Cards
9780559122774: The Tarot: History, Symbolism, And Divination
9780517503812: A History of Playing Cards
9780486996479: Antique Playing Card Designs Cd-Rom And Book (Dover Electronic Clip Art)
9780486292656: Antique Playing Cards: A Pictorial History
Created03-15-2012 1:05:00am
Modified04-30-2020 9:11:07pm
MD52a211dc67e9a26eb3532c3434c7d632a
SHA2564c9c08048754972d0cb9e8b21d6d321df460bbd146a3d0c93951faa5d861960c
Search Googleby EAN or by Title
Query Time0.0217950

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