Image
EAN-130883904333135   EAN-13 barcode 0883904333135
UPC-A883904333135   UPC-A barcode 883904333135
Product NameGoldeneye
CategoryElectronics / Photography: A/V Media: Movie / TV
Amazon.comA Buy on Amazon ~ B011MHCNOA
Model35224912
Price New5.10 US Dollars    (curriencies)
Price Used3.49 US Dollars    (curriencies)
RatingPG-13 - Parents Strongly Cautioned
IMDbIMDb Link
TrailerWatch The Trailer
Run Time130 minutes
CastPierce Brosnan, Sean Bean, Izabella Scorupco, Famke Janssen
DirectorMartin Campbell
GenreACTION,ADVENTURE,THRILLER
Width5.5 inches    (convert)
Height0.5 inches    (convert)
Length7.5 inches    (convert)
Weight15 hundredths pounds    (convert)
BindingDvd
Release Year1995
FormatMultiple Formats, Color, Widescreen, NTSC
Published09/15/2015
FeaturesShrink-wrapped
Long DescriptionWhen a deadly satellite weapon system falls into the wrong hands, only Agent 007 can save the world from certain disaster. Armed with his license to kill, Bond races to Russia in search of the stolen access codes for "Goldeneye," an awesome space weapon that can fire a devastating electromagnetic pulse toward Earth. But 007 is up against an enemy who anticipates his every move: a mastermind motivated by years of simmering hatred. Bond also squares off against Xenia Onatopp, an assassin who uses pleasure as her ultimate weapon.
Similar Items9780792856115: Die Another Day (Widescreen Special Edition)
0883904333432: Casino Royale
0883904333333: View to a Kill, A
0883904333319: Thunderball
0883904333234: Moonraker
0883904333197: Living Daylights, The
0883904333050: Tomorrow Never Dies
0883904333036: Licence to Kill
0883904333012: World Is Not Enough, The
0027616884282: Die Another Day (Widescreen Special Edition)
0027616066275: Goldfinger
Created04-27-2018 1:29:42am
Modified05-05-2019 12:59:33pm
MD5671ec85a9b902a5124b82d2a8f8df047
SHA256c58ae850597d182e6784d38bc0fdd04e991ec3a73ecfcb3eb74e43b7b2819e86
Search Googleby EAN or by Title
Query Time0.0218689

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