Image
EAN-139780739413012   EAN-13 barcode 9780739413012
Product NameRingworld: A Novel
LanguageEnglish
CategoryBook / Magazine / Publication
Amazon.comA Buy on Amazon ~ 0030206561
SKU6435694
Price New60.33 US Dollars    (curriencies)
Price Used1.28 US Dollars    (curriencies)
AuthorLarry Niven
Page Count342
BindingHardcover
Published08/01/1977
Long Description**Best Novel 1970 Nebula Award **Best Novel 1971 Hugo Award The artifact is a vast circular ribbon of matter, some 180 million miles across, with a sun at its center. Pierson's puppeteers--strange, three-legged, two-headed aliens--discovered this ''Ringworld'' in a hitherto unexplored part of the galaxy. Curious about the immense structure, but frightened by the prospect of meeting the builders, they set about assembling a team to explore it: -Louis Wu, human -- old and bored with having lived too fully for too many years, seeking an adventure, and all too capable of handling it. -Nessus, puppeteer -- a trembling coward from a species with an inbuilt survival pattern of nonviolence. This particular puppeteer, however, is insane. -Speaker-to-Animals, kzin -- large, orange-furred, and carnivorous. The kzin are one of the most savage life-forms known. The party's expedition, however, goes disastrously wrong when their ship crash-lands and its motley crew faces a daunting trek across thousands of miles of Ringworld territory.
Similar Items9780765326089: Betrayer Of Worlds (Known Space)
9780765322050: Destroyer Of Worlds
9781127105915: A Canticle For Leibowitz
9780839823094: A Canticle for Leibowitz (The Gregg Press Science Fiction Series)
9780932096036: The Ringworld Engineers
9780030213762: The Ringworld Engineers
9780888995971: Fate of Worlds: Return from the Ringworld (Known Space)
9780765331007: Fate of Worlds: Return from the Ringworld (Known Space)
9780765318268: Juggler Of Worlds: 200 Years Before The Discovery Of The Ringworld
9780765318251: Fleet of Worlds (Known Space)
9780765301673: Ringworld's Children
9780345358615: Ringworld Throne
9780965018852: The Man In The High Castle (S.F.Masterworks) U.K.
Created11-22-2012 1:59:30am
Modified05-01-2020 12:14:41am
MD5e0338a5125428a4e15269277415d4bfa
SHA25674b152994a636e5747f0bfc17e24fcb7362fe6c89afaeb239179d0cc51741d67
Search Googleby EAN or by Title
Query Time0.0277619

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

Close

Dialog