Disable All Advertising
Image
EAN-130018713583406   EAN-13 barcode 0018713583406
UPC-A018713583406   UPC-A barcode 018713583406
Product NameUltimate Guide: Dolphins
CategoryElectronics / Photography: A/V Media: Movie / TV
Short DescriptionDVD
Amazon.comA Buy on Amazon ~ B0050QNO7A
SKU018713583406
Price New7.98 US Dollars    (curriencies)
Price Used9.97 US Dollars    (curriencies)
Long DescriptionPeaceful, intelligent, friendly beings that swim as if they owned the sea, dolphins have long evoked our affection and fascination, but we know little about them. Ultimate Guide takes a fresh look at the world of the dolphins and meets up with scientists who are deepening our understanding of them. Sonar engineer Dave Gordon believes that the key to dolphin echolocation is the teeth in their lower jaw, which they use like a TV antenna. Researchers at Texas A&M have strapped cameras to dolphins to solve the mystery of their deep diving ability. And scientists in Scotland have collected evidence of a darker side to the dolphin's personality, including vicious bite marks on young dolphins and amateur videotape of a group of dolphins torturing and killing porpoises. With cutting-edge computer animation, Ultimate Guide shows what happened fifty million years ago, when a wolf-like mammal took to foraging in swamps and estuaries: It lost its back legs and its fur; its nostrils fused and became a blowhole; its front legs turned into flippers; and it learned to swim with less effort than any fish. Over eons, in short, these creatures evolved into the family of dolphins, porpoises, and killer whales.
Similar Items5060052415394: Eye of the Dolphin
0872322009968: 20 Years With The Dolphins
0012233141023: Eye of the Dolphin
Created04-17-2012 8:43:45pm
Modified10-04-2017 4:47:42pm
MD5f7062d361aae86c4cef369dd7227d90d
SHA2561472ce3264fc423f5c237e8ea1d88bd3042f6f582e1e0a7653d90313f9b6179b
Search Googleby EAN or by Title
Query Time0.0123630

An article of interest

Making use of the tools we offer

Data Feed API v3 - Access and Data Layout

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.