Changes between Version 7 and Version 8 of NativeGateway

Timestamp:

Nov 4, 2010, 8:42:25 AM (14 years ago)

Author:

zach

Comment:

--

NativeGateway

@@ -56 +56 @@
 Command line options:
 -p HTTPD port (default 8000)
--s HTTPD hostname for inserting in resource desciptions (default localhost)
+-s HTTPD hostname for inserting in resource desciptions as &ipaddress (default localhost)
 
 The SENSEI HTTP server runs by default on port 8000. Just browse 
@@ -70 +70 @@
 == Sensei Plugin ==
 
-The SENSEI Plugin handles BinaryWS interfaces to 6LoWPAN nodes. The plugin automatically collects published resource descriptions from nodes, registers them with HTTP resource access interfaces, and then handles proxy transformations in both directions. 
+The SENSEI Plugin handles CoAP interfaces to 6LoWPAN nodes. The plugin automatically collects published resource descriptions from nodes, registers them with HTTP resource access interfaces, and then handles proxy transformations in both directions. 
 
 The plugin prepends HTTP resources with /node{ID} where ID is a generated unsigned integer. Thus a resource from a sensor node on URL /s/temp would be published as e.g. /node1/s/temp to the RD. There is a 1-1 mapping between each node{ID} and the IPv6 address of a 6LoWPAN node.
@@ -84 +84 @@
  * /stats - XML output of statistics from the plugin
  * /rd - List of all resource descriptions published by the plugin
- * /localhost/s/temp - Test resource which always requests /s/temp from ::1 (for use with binaryWS_test)
+ * /localhost/s/temp - Test resource which always requests /s/temp from ::1 
 
 === eRPI Interface ===
@@ -143 +143 @@
 Requests coming from the RAI interface are matched with registered URLs (registered from resource descriptions sent by nodes), and then as CoAP requests to the corresponding WSAN node and URL. The response is returned to the resource user. When caching is implemented a cache for each resource will be checked first before making a CoAP request.
 
-Sensor nodes may also make binaryWS 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 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.