Image
EAN-139780440845645   EAN-13 barcode 9780440845645
Product NameDiners, Drive-Ins, And Dives: The Funky Finds In Flavortown: America's Classic Joints And Killer Comfort Food
LanguageEnglish
CategoryBook / Magazine / Publication
Amazon.comA Buy on Amazon ~ 0062244655
Price New7.98 US Dollars    (curriencies)
Price Used2.97 US Dollars    (curriencies)
Width0.8 inches    (convert)
Height9.13 inches    (convert)
Length7.38 inches    (convert)
Weight19.2 ounces    (convert)
AuthorGuy Fieri, Ann Volkwein
Page Count320
BindingPaperback
Published05/14/2013
FeaturesWilliam Morrow Company
Long DescriptionSomething Special for Me
Similar Items9780307591241: Roadfood: The Coast-To-Coast Guide To 800 Of The Best Barbecue Joints, Lobster Shacks, Ice Cream Parlors, Highway Diners, And Much, Much More
9780848739553: Southern Living Off The Eaten Path: Second Helpings: Tasty Eats And Delicious Stories From The South's Less-Traveled Trails (Southern Living (Paperback Oxmoor))
9780061894558: Guy Fieri Food: Cookin' It, Livin' It, Lovin' It
9780061724886: Diners, Drive-ins and Dives: An All-American Road Trip . . . with Recipes!
9780760324349: Diners, Drive-ins and Dives: An All-American Road Trip . . . with Recipes!
9780746010693: Diners, Drive-ins and Dives: An All-American Road Trip . . . with Recipes!
9780554510392: Diners, Drive-ins and Dives: An All-American Road Trip . . . with Recipes!
9780554510361: Diners, Drive-ins and Dives: An All-American Road Trip . . . with Recipes!
9780770434526: Roadfood: The Coast-To-Coast Guide To 900 Of The Best Barbecue Joints, Lobster Shacks, Ice Cream Parlors, Highway Diners, And Much, Much More, Now In Its 9th Edition
9781450817691: Where America Eats: Burger Joints, Bbq Shacks, Sandwich Shops
View 64 more similar items
Created07-18-2013 3:27:26pm
Modified05-16-2017 9:07:26am
MD5fb453cd6db41c92de13d9191a62d5563
SHA256b3618e71e0399e5514e7aef8ff04b07bf28496a78740e0bdc437537fbb4608cd
Search Googleby EAN or by Title
Query Time0.0215771

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

Close

Dialog