Changes between Version 9 and Version 10 of NativeGateway

Timestamp:

Nov 4, 2010, 8:45:26 AM (14 years ago)

Author:

zach

Comment:

--

NativeGateway

@@ -88 +88 @@
 === eRPI Interface ===
 
-Nodes publish their resource description to the Gateway upon initialization and periodically (before Expiration-Time). This is sent to the URL /rpi[0] ([0] refers to compressed URL code 0) on the gateway (port 61626). 
+Nodes publish their resource description to the Gateway upon initialization and periodically (before Expiration-Time). This is sent to the URL /rpi![0] (![0] refers to compressed URL code 0) on the gateway (port 61626). 
 
-The gateway stores resource descriptions locally in /xml and supports fetching descriptions from an http:// URL (not yet implemented). Sensor nodes do not send full resource descriptions, but instead only a Document-Link to the description. The body of the CoAP message POSTed to /rpi must contain the string:
+The gateway stores resource descriptions locally in /xml and supports fetching descriptions from an !http:// URL (not yet implemented). Sensor nodes do not send full resource descriptions, but instead only a Document-Link to the description. The body of the CoAP message POSTed to /rpi must contain the string:
 
 {{{
@@ -145 +145 @@
 Sensor nodes may also make CoAP requests outside the WSAN island (proxied to HTTP) by including a full FQDN URL (www.example.com/test) in the URL field of the CoAP request header. This feature is not yet supported. 
 
-Sensor nodes may send evenets without a subscription to a notification collector on the gateway by POSTing to /notify[1]. The evenet is POSTed to a default event collection service on the SENSEI Management Web-page. The body may be any O&M content or even text/plain.
+Sensor nodes may send evenets without a subscription to a notification collector on the gateway by POSTing to /notify![1]. The evenet is POSTed to a default event collection service on the SENSEI Management Web-page. The body may be any O&M content or even text/plain.