Image
EAN-130014381797022   EAN-13 barcode 0014381797022
UPC-A014381797022   UPC-A barcode 014381797022
Product NameDavid E. Talbert's Another Man Will
CategoryElectronics / Photography: A/V Media: Movie / TV
Amazon.comA Buy on Amazon ~ B01M26ELL3
Model43379586
Price New5.01 US Dollars    (curriencies)
Price Used4.58 US Dollars    (curriencies)
Run Time102 minutes
CastAndra Fuller, Jason Weaver, Nadine Ellis, Teresa Sykes, Thomas Nephew Tommy Miles
GenreComedies
Run Time102 minutes
Width5.5 inches    (convert)
Height0.75 inches    (convert)
Length7.5 inches    (convert)
Weight20 hundredths pounds    (convert)
BindingDvd
FormatColor, Dolby, NTSC, Widescreen
Run Time102 minutes
FeaturesShrink-wrapped
Long DescriptionJoe (Thomas "Nephew Tommy" Miles) and Cynthia Scott (Nadine Ellis) are the perfect couple…or at least nineteen years ago they were. Somewhere in the routine of it all, Joe has forgotten just how much of a knockout his wife really is. Unfortunately for him, their ruggedly handsome gardener hasn’t. Lovely once, lovely still…treat her right or another man will. Featuring an all-star cast inlcuding Jason Weaver, Andra Fuller, Teresa Sykes and KJ Smith.
Similar Items9781404986251: Brothers in Arms
0687797166296: Love Won't Let Me Wait
0043396471153: When the Bough Breaks
0043396449190: With This Ring
0031398256885: Tyler Perry's Madea On The Run
0031398222873: Pastor Brown/ Sins of the Mother - Double Feature
0025192347191: Almost Christmas
0014381865325: David E. Talbert Triple Feature (What My Husband Doesn't Know / Suddenly Single / A Fool and His Money)
0014381666229: David E. Talbert's Mr Right Now
0014381666120: David E. Talbert's Love in the Nick of Tyme
0014381326628: Men Cry in the Dark
0014381000542: Double Feature
0012236113744: My Girlfriend's Back
Created04-12-2018 12:40:52am
Modified04-18-2019 7:23:28am
MD5568a55b2e35337d5ffa301138542565d
SHA256a072a4d8510661c211e27def0c7f4b208c7add0914f22048a3fc6169baf092dd
Search Googleby EAN or by Title
Query Time0.0203221

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