Changes between Initial Version and Version 1 of RpRepDeployment


Ignore:
Timestamp:
Sep 30, 2010, 9:09:39 PM (14 years ago)
Author:
s.meissner
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • RpRepDeployment

    v1 v1  
     1The Resource Endpoint (REP) provides a standardised access to the sensors inside the test bed which are exposed as SENSEI Resources. The Resource Access Interface (RAI) is the standard RESTful interface provided to SENSEI users.
     2
     3Each sensor of the test bed will have a counterpart on the REP modelled as a Resource. One REP can accommodate more Resources. A router will take care that a REST call will be directed to the Resource the call concerns.
     4
     5Once a method on a Resource is called, the call will be translated into the proprietary call the sensor island gateway is able to handle. This Gateway inside the test bed will forward the call to the desired sensor.
     6
     7
     8The REP is basically the adapter to the SENSEI system that needs to be implemented. The Java REP reference implementation provides some helpers to the Resource Providers. The stubs for RPI and RAI methods are given in the example code.
     9
     10RPI methods:
     11•       public List<String> publishResourceDescription(String descriptionString)
     12•       public List<String> publishResourceDescription(ResourceDescription desc)
     13•       public String updateResourceDescription(String resourceID, ResourceDescription description)
     14•       public String deleteResourceDescription(List<String> resourceIDs)
     15
     16The RAI methods are provided by the RAIHandler that is attached to the REP. The RAIHandler is the Resource the REP exposes to the SENSEI Resource Users. In the example project a com.sensinode.sensei.rep.rest.test.SensorType.class is attached to the REP.
     17
     18SensorTypes' GET requests are handled by its method:
     19•       public Representation represent(Variant variant)
     20This method returns the Observation & Measurement value in XML/RDF format.
     21
     22POST requests are handled by:
     23•       public void acceptRepresentation(Representation entity)
     24
     25The POST request is meant to be used to subscribe to sensor readings. A subscription needs to be sent in the POST body. The subscription handling is not yet standardised.
     26
     27The describeXXX methods in the SensorType class are used to create a WADL description of the Resource's RAI interface. In the currently used version of the Restlet framework the WADL support is not yet finalised, so that the WADL support cannot be guaranteed.