Difference between revisions of "Tech pages/IoT HttpOverXmpp"

Jump to navigation Jump to search

Tech pages/IoT HttpOverXmpp (view source)

Revision as of 16:09, 29 July 2013

1,444 bytes added ,  16:09, 29 July 2013
no edit summary
Line 10: Line 10:
   [[Tech pages/IoT_HttpOverXmpp|IoT_HttpOverXmpp]] This extension creates a view of webservices through the XMPP network
   [[Tech pages/IoT_HttpOverXmpp|IoT_HttpOverXmpp]] This extension creates a view of webservices through the XMPP network


= Introduction =
== Introduction ==


Setting up IoT devices as ordinary HTTP accessible servers, both over IPv4 and IPv6 exposes those devices to the whole internet unless you take special care of the traffic in a router or firewall.


To Be Added
with the usage of the [http://xmpp.org/extensions/xep-0332.html | XEP-0332 HTTP over XMPP] extension it is possible to provide a protected pathway to the device.


The XMPP protocol does not have the same problems as HTTP in these regards. It's a peer-to-peer like protocol naturally allowing communication with applications and devices behind firewalls. It also includes advanced user authentication and authorization which makes it easier to make sure unauthorized access to private content is prevented.


there are many aims in fact.
Furthermore, with the advent of semantic web technologies and its use in web 3.0 and Internet of Things applications, such applications move even more rapidly into the private spheres of the users, where security and privacy is of paramount importance, it is necessary to use more secure transport protocols than HTTP over TCP.


But one aim is to be able to move existing applications (web applications, web services, semantic applications, etc. hosted on the web) and move them into new settings (for instance hosting it at home) and be able to reuse them without having to change them or opening ports in firewalls. An example would be to access your thermostat (that has a built in web page) from your office.
There are examples of other protocols transported over XMPP [http://xmpp.org/extensions/xep-0072.html | XEP-0072 SOAP Over XMPP]


There are many different types of HTTP-based communication that could be transported


Another aim is to be able to create new applications (web applications, web services, semantic applications) and be able to use them both on the web, but also safely for instance hosting them at home, and accessing them from the outside without having to code explicitly for this. It would be automatic, through the use of xmpp:// URL scheme.
* Web Content like pages, images, files, etc.
* Web Forms.
* Web Services (SOAP, REST, etc.)
* Semantic Web Resources (RDF, Turtle, etc.)
* Federated SPARQL queries (SQL-type query language for the semantic web, or web 3.0)
* Streamed multi-media content in UPnP and DLNA networks.


But instead of trying to figure out all possible things transportable over HTTP and make them transportable over XMPP, this document ignores the type of content transported, and instead focuses on encoding and decoding the original HTTP requests and responses, building an HTTP tunnel over an existing XMPP connection.


The only implementation required is to implement support for it in the corresponding web server (for instance open source Apache) and a browser (open source Fire Fox, Chromium, for instance), instead of having to implement peer-to-peer technology into the application itself (or all the applications themselves - thousands, tens of thousands, hundreds of thousands, millions?).
It would enable existing applications to work seamlessly over XMPP if browsers and web services supported this extension (like displaying your home control application on your phone when you are at work), without the need to update the myriad of existing applications. It would also permit federated SPARQL queries in personal networks with the added benefit of being able to control who can talk to who (or what can talk to what) through established friendship relationships.


This making it possible to move existing applications (web applications, web services, semantic applications, etc. hosted on the web) and move them into new settings (for instance hosting it at home) and be able to reuse them without having to change them or opening ports in firewalls. An example would be to access your thermostat (that has a built in web page) from your office.


Another aim is to extend semantic technologies from HTTP to XMPP, to be able to create more secure applications, for instance in the Internet of Things.
== Added URI ==
 
== How it works ==
Jocke
16

edits

Retrieved from "https://wiki.xmpp.org/web/Special:MobileDiff/7712"

Navigation menu