EAN-139780764340888   EAN-13 barcode 9780764340888
Product NameVintage North End, Virginia Beach: An Illustrated History
CategoryBook / Magazine / Publication
Short DescriptionHeight:0 inches / Length:0 inches / Weight:0 pounds / Width:0 inches
Amazon.comA Buy on Amazon ~ 0764340883
Price New22.30 US Dollars    (curriencies)
Price Used17.24 US Dollars    (curriencies)
Width8.99 inches    (convert)
Height0.79 inches    (convert)
Length11.27 inches    (convert)
Weight41.76 ounces    (convert)
AuthorAnn Hanbury Callis, Danna Cullen
Page Count168
FeaturesUsed Book in Good Condition
Long DescriptionVirginia Beach comes alive in this illustrated history starting in the early 20th century. Revisit popular landmarks like Holland s General Store, Piney Point Club, and the Waverly and Cavalier Hotels. Through 466 images, learn about the people who lived here and made Virginia Beach what it is today. From the famous cottages of the North End, to the glamour girls enjoying the beach and the Big Band sounds at the local nightclubs, fun and historical facts about the area and its founding families will both entertain and educate. For past and current residents of the North End, tourists, history buffs, and genealogists.
Similar Items9780898657432: Princess Anne County And Virginia Beach: A Pictorial History
9781609492045: Lost Virginia Beach
9780738566498: Virginia Beach (Then and Now)
9780738541754: Virginia Beach: Jewel Resort of the Atlantic (VA) (Images of America)
9780738517162: Virginia Beach in Vintage Postcards (VA) (Postcard History Series)
9781596523326: Historic Photos Of Norfolk
9781596298507: Lost Norfolk
9780764329999: Greetings from Virginia Beach (Greetings From... (Hardcover))
Created11-22-2012 10:23:02am
Modified09-30-2017 7:13:42pm
Search Googleby EAN or by Title
Query Time0.0194480

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.