User login

Weekly Report - 19/09/14




I used an interview in Sydney to procrastinate for most of this week...

Spent some time looking into HTTP/CoAP proxies. The Java-based Californium project seems the most well-established (although there seems to be little to compare it to). I got it up and running and it works nicely as a proxy, but it isn't completely seamless (i.e. resources are accessed on remote CoAP servers via addresses such as http://proxy_host/[coap_host]/resource, as opposed to http://[coap_host]/resource). I would have liked to have more time to investigate setting up a transparent proxy, but then again, I don't think direct HTTP/CoAP proxies are an intended use case for the Internet of Things - rather, an indirect proxy featuring caching (load balancing for the embedded network) and returning "prettier" data to the client would be more useful. At least with this experience I'll have something to discuss in my report.

A disadvantage of the Java proxy is that it runs separately to Contiki/6LBR, which has full control over the network interfaces. This means the CoAP proxy must be run on separate hardware to the 6LBR. In an ideal system this proxy would run as a Contiki process.