#### Client Side
**CoapClient (interface):** describes interfaces that must be supported by a client
**Client:** individual implementation of a client application, implements CoapClient (interface)
**ChannelManager:** manages channels
**Channel:** one channel represents a connection to one client
#### Server Side
**CoapResource (interface):** describes interfaces that must be supported by each resource.
**CoapClient:** Interface that must be implemented by a client
**BasicCoapResource:** already implemented resource with basic functionality, implements CoapResource (interface)
**Client:** Customized implementation of a client application, implements `CoapClient`
**TemperatureResource:** individual resource, inherits from BasicCoapResource
**Channel:** A channel represents a connection between a Client and a Server
**CoapServer (interface):** describes interfaces that must be supported by a resource server
**ChannelManager:** Manages `Channels` (Timeouts, Matching Requests and Responses)
**CoapResourceServer:** manages a list of resources, enables access of these resources from outside, implements CoapServer (interface)
**Server:** individual implementation of a server application, creates CoapResourceServer and resources
* ToDo on server side:
1. Create a new resource class TemperatureResource
2. Instantiate a new ResourceServer
3. Instantiate a new TemperatureResource
4. Add the TemperatureResource to the ResourceServer
5. Run the ResourceServer
#### Server Side
* ToDo on client side:
**CoapResource:** Interface that must be supported by each resource.
1. Establish a connection to the Server using the ChannelManager
**BasicCoapResource:** Already implemented resource with basic functionality, implements `CoapResource`
2. Create a CoapRequest & add some Options
**TemperatureResource:** Example of a customized resource, inherits from `BasicCoapResource`
3. Send the CoapRequest
**CoapServer:** Interface that must be supported by a resource server
4. Wait for CoapResponse
**CoapResourceServer:** Manages a list of resources, enables access of these resources from outside, implements `CoapServer`
5. Print the CoapResponse on the console
**Server:** Example of a customized implementation of a server application, creates `CoapResourceServer` and `CoapResources`
## 4. Import of prepared project into Eclipse
## 4. Import of prepared project into Eclipse
You can find the required files in our repository at https://gitlab.amd.e-technik.uni-rostock.de/ws4d/jcoap/tree/master/ws4d-jcoap-handsOn
You can find the required files in our repository at [https://gitlab.amd.e-technik.uni-rostock.de/ws4d/jcoap/tree/master/ws4d-jcoap-handsOn](https://gitlab.amd.e-technik.uni-rostock.de/ws4d/jcoap/tree/master/ws4d-jcoap-handsOn)
3. Implement an Air Conditioner Resource with the path “/ACControl”, that can be set to “high”, “medium”, “low” or “off” (Client.java & Server.java, TODO 12-15):
}
```
3. Implement an Air Conditioner Resource with the path `/ACControl`, that can be set to `high`, `medium`, `low` or `off` (Client.java & Server.java, TODO 12-15):
* Change exitAfterResponse to false (Client.java, TODO 12)
* Change exitAfterResponse to false (Client.java, TODO 12)
* Add the observe-option to your CoAP-GET request (Client.java, TODO 13)
* Add the observe-option to your CoAP-GET request (Client.java, TODO 13)
`request.setObserveOption(0);`
```java
* add a BasicCoapResource to the ResourceServer (Server.java, TODO 14) `resourceServer.createResource(newBasicCoapResource(“/ACControl”,”off”,CoapMediaType.text_plain));`
