Changes between Version 9 and Version 10 of RpRepDeployment
- Timestamp:
- Oct 20, 2010, 12:59:58 PM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
RpRepDeployment
v9 v10 39 39 The parameter sensor Name is taken from the URL used for the HTTP request so that the route can be used for temperature values as well as light values. In the first case the request would be http://{REP_URL}/s/temp in the light value case it would be http://{REP_URL}/s/light. 40 40 41 The different handling for temp and light is implemented in the **RAI handler** class called Sensor Typein the example code.41 The different handling for temp and light is implemented in the **RAI handler** class called **Sensor Type** in the example code. 42 42 43 43 === Resource Access Interface === … … 46 46 In the example project a **com.sensinode.sensei.rep.rest.test.SensorType.class** is used as an example for a RAI handler attached to the REP. 47 47 48 '''RAI GET''' requests are handled by the method **toXML()** provided by the class **Sensor Type**. This method re turns the Observation & Measurement valuein XML/RDF format.48 '''RAI GET''' requests are handled by the method **toXML()** provided by the class **Sensor Type**. This method reads the Observation & Measurement value from a file and returns in XML/RDF format. 49 49 50 50 {{{ … … 94 94 === Resource Publish Interface === 95 95 96 Also part of the example code is the class **RPI Client** which provides the methods to publish and unpublish Resource Descriptions to Resource Directories. 97 96 98 * public List<String> publishResourceDescription(String descriptionString) 97 99 * public List<String> publishResourceDescription(ResourceDescription desc) 98 100 * public String updateResourceDescription(String resourceID, ResourceDescription description) 99 101 * public String deleteResourceDescription(List<String> resourceIDs) 102 103 On how to write Resource Descriptions please see section [[wiki:ResourceDescription]]