What is ZigBee?
What is IEEE 802.15.4?
How is ZigBee different from other wireless standards (e.g. Bluetooth)?
What are the real-life applications of ZigBee?
How reliable is the data delivery?
How long is the battery life?
What are the cost considerations for ZigBee implementation?
How long is the Transmission Range?
How high is the Data Rate?
What is the Data Latency for ZigBee Networks?
How large/small a ZigBee Network can be?
How is the Data Security provided?
What is ZigBee Stack?
What Subunits can be on a Node?
What is called ZigBee Application?
What are the ZigBee Device Descriptors?
What is ZigBee Device Profile?
What is ZigBee Stack Profile?
What are the ZigBee Device Objects?
How does a Device/Service Discovery process work?
What are the Clusters, ZigBee Binding and Binding Table?
How is Addressing and Messaging done in a ZigBee network?
What types of ZigBee Devices exist in a network?
What Topologies are supported by ZigBee?
What is ZigBee network Gateway?

Amadah, Blaauw & Brooks

"In REST, “post” is used for any action which results in a resource change or side-effect, and cannot be repeated without the change or side-effect happening again. An SQL “insert” operation would be implemented as a REST “post”, for example, but so would an SQL “update” which increments a value, or the sending of an email. A practical rule of thumb is that a “post” should be simple and quick, leaving the way for future changes using “put” as soon as possible. A CRUD “create” is a quite different thing. “Create” explicitly creates a new resource, and is undefined if that resource already exists."

" - searched - retrieved details - reserved These states map to URIs: - http://quuxTravel.com/searched - ??? depends on previous state - ??? depends on previous state " via http://devhawk.net/2007/05/24/REST+Is+Neither+CRUD+Nor+CRAP.aspx

"Details In MySQL, our entities are stored in a table that looks like this: CREATE TABLE entities ( added_id INT NOT NULL AUTO_INCREMENT PRIMARY KEY, id BINARY(16) NOT NULL, updated TIMESTAMP NOT NULL, body MEDIUMBLOB, UNIQUE KEY (id), KEY (updated) ) ENGINE=InnoDB; For example, a typical entity in FriendFeed might look like this: { "id": "71f0c4d2291844cca2df6f486e96e37c", "user_id": "f48b0440ca0c4f66991c4d5f6a078eaf", "feed_id": "f48b0440ca0c4f66991c4d5f6a078eaf", "title": "We just launched a new backend system for FriendFeed!", "link": "http://friendfeed.com/e/71f0c4d2-2918-44cc-a2df-6f486e96e37c", "published": 1235697046, "updated": 1235697046, } "

From the source. Parleys.com sure has an annoying UI.

via http://parleys.com/display/PARLEYS/Home#slide=8;title=REST%20-%20The%20Better%20Web%20Services%20Model;talk=6451 "So, in order to prove the point that SOAP should not be compared against REST, I decided to do some coding. Since I had just finished the implementation of WS-Transfer for PlumbworkOrange, I thought that it would be a great idea to use it to build a RESTful application. And of course, what's the most well-known application out there? The Web of course. WS-Web The idea is based on the following: * Follow the REST principles for building the WWW but using SOAP and without assuming HTTP. * The uniform application semantics of WS-Transfer are assumed. * Each resource is still associated with its own URI although now the URI can be application/transport-protocol independent (e.g. urn:uuid:bla-bla-bla-bla). This has the advantage that the name or identifier of a resource is not coupled with the technology used to access it."