Disable All Advertising
Image
EAN-139780133142785   EAN-13 barcode 9780133142785
Product NameFiber-Optic Communication Systems
CategoryBook / Magazine / Publication
Short DescriptionHardcover
Amazon.comA Buy on Amazon ~ 0470505117
SKU0929-WS1201-A04010-0133142787
Price New113.39 US Dollars    (curriencies)
Price Used111.08 US Dollars    (curriencies)
Width1.7 inches    (convert)
Height9.4 inches    (convert)
Length6.1 inches    (convert)
Weight25.6 ounces    (convert)
AuthorGovind P. Agrawal
Page Count626
BindingHardcover
Published10/19/2010
Long DescriptionThis book provides a comprehensive account of fiber-optic communication systems. The 3rd edition of this book is used worldwide as a textbook in many universities. This 4th edition incorporates recent advances that have occurred, in particular two new chapters. One deals with the advanced modulation formats (such as DPSK, QPSK, and QAM) that are increasingly being used for improving spectral efficiency of WDM lightwave systems. The second chapter focuses on new techniques such as all-optical regeneration that are under development and likely to be used in future communication systems. All other chapters are updated, as well.
Similar Items9780792397533: Microwave Engineering
9780572018108: Microwave Engineering
9780470631553: Microwave Engineering
9780155586581: Microwave Engineering
9780135816950: Microwave Engineering
9780135812075: Microwave Engineering
9780134878430: Microwave Engineering
9780195179460: Photonics: Optical Electronics in Modern Communications (The Oxford Series in Electrical and Computer Engineering)
9780123740922: Optical Networks: A Practical Perspective, 3rd Edition
9780387261416: Optical Networks: A Practical Perspective, 3rd Edition
View 44 more similar items
Created07-31-2012 1:05:00am
Modified09-03-2017 8:37:04am
MD52470dff754b8e7b6384c3aa4708eab4e
SHA25615c8675b160e87e327972e303100bb8e601359452aba9118e6f8e6954cb22680
Search Googleby EAN or by Title
Query Time0.0279009

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.