Image
EAN-139781621050872   EAN-13 barcode 9781621050872
Product NameShatnerquest
CategoryBook / Magazine / Publication
Short DescriptionHeight:8.5 inches / Length:5.51 inches / Weight:0.5 pounds / Width:0.39 inches
Amazon.comA Buy on Amazon ~ 1621050874
Price New10.95 US Dollars    (curriencies)
Price Used3.12 US Dollars    (curriencies)
Width0.4 inches    (convert)
Height8.5 inches    (convert)
Length5.51 inches    (convert)
Weight7.84 ounces    (convert)
AuthorJeff Burk
Page Count188
BindingPaperback
Published04/01/2013
FeaturesUsed Book in Good Condition
Long DescriptionWilliam Shatner? William Shatner. William Shatner!

After the apocalypse, three Star Trek fans and their morbidly obese cat embark on a quest to save their beloved idol, the one and only William Shatner, from the hostile world America has become.

But their journey will not be easy, for the wasteland is filled with cannibal cults, Klingon biker gangs, Zombie Borg, and all manner of mutant creatures. And once they arrive at their destination, they discover that William Shatner has been transformed into Shatzilla - a giant 100-story radioactive monster hell-bent on destroying all of Los Angeles.

Now instead of saving Shatner from this new apocalyptic world, these three fans must save the world from this new apocalyptic Shatner. If only there was another giant monster who could take him down...

From the author who brought you the cult hit Shatnerquake, comes another Shat-tastic sci-fi comedy that proves once and for all that there actually is something even bigger than William Shatner's ego. And it is... William Shatner!
Similar Items9781936383863: Cripple Wolf
9781936383825: I Knocked Up Satan's Daughter: A Demonic Romantic Comedy
9781933929965: Super Giant Monster Time! (Choose Your Own Mind-Fuck Fest #3)
9781594744631: Night Of The Living Trekkies (Quirk Fiction)
9781936383542: Walrus Tales
9781933929828: Shatnerquake
Created05-05-2013 12:33:54am
Modified09-09-2017 9:00:14am
MD5a2dcc502262a58a55402dcc6279b86c4
SHA25616123d62791c5150ee1dc0fe68039c75b96488e611b280a837ccb4e59d704147
Search Googleby EAN or by Title
Query Time0.0105329

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.

Close

Search

Close

Share

Close

Dialog