Re: [6lowapp] Really we need for HTTP on smart devices?

Hi Adriano,

We spent some time looking at the options for message exchange in Smart
Energy V2.  We knew we would be using self describing data (XML most likely)
and looked at the technologies that would allow the best integration with
existing internet/web solutions (basically trying to avoid a proprietary
binary protocol if we could).

I agree full HTTP would be too heavy on a small device.  However, using a
minimal set of HTTP features and a REST data exchange paradigm seemed to be
the most elegant solution.  I don't expect each device to host a web server
but I would expect some devices to do so  It just seemed that if we could
align on a known, deployed standard, adapted for small devices, we would
gain a lot in adoption.

Don

-----Original Message-----
From: 6lowapp-bounces@ietf.org [mailto:6lowapp-bounces@ietf.org] On Behalf
Of Adriano Pezzuto (apezzuto)
Sent: Friday, October 30, 2009 5:03 AM
To: 6lowapp@ietf.org
Subject: [6lowapp] Really we need for HTTP on smart devices?

Hello,
there is a lot effort to push HTTP and REST interfaces on smart objects
assuming that smart devices (sensor/actuators/readers) should act as Web
providers. On the other side, 6lowpan and other wireless sensor networks
are made by resource-constrained embedded devices so HTTP looks like too
resource expensive.

We are seeing a lot of proxying and gatewaying solutions to bring HTTP
and REST on the 6lowpan devices. But working with gateways and proxies
are always struggling especially at application level. My question here
is why we need to bring HTTP on smart objects?

Smart objects interact with the Internet as they like (and can) as
humans do. Humans type on a computer keyboard or play in front of the
iPhone camera while Things send sensing data or get commands to act on
the real world. Humans do not have an embedded HTTP server even if the
results of their actions (i.e. typing on a keyboard and playing in front
of a camera) are available as Web resources. In the same way, Things do
not need for an embedded HTTP server. Things interact with the Internet
using a lightweight protocol while the results of their interaction are
available on the Web as resources. It is a sort of "information shadow"
data that Things have on the Web. This data will be collected in a
suitable manner for the resource-constrained embedded devices and make
available as Web resource with HTTP and REST interfaces.

What do you think about it?

Regards,
Adriano

_______________________________________________
6lowapp mailing list
6lowapp@ietf.org
https://www.ietf.org/mailman/listinfo/6lowapp