Difference between revisions of "Tech pages/IoT HttpOverXmpp"

Jump to navigation Jump to search

Tech pages/IoT HttpOverXmpp (view source)

Revision as of 16:19, 29 July 2013

419 bytes removed ,  16:19, 29 July 2013
no edit summary
Line 31: Line 31:
* Streamed multi-media content in UPnP and DLNA networks.
* 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.


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.
But instead of looking at all possible HTTP transports and make them transportable over XMPP, this document ignores the type of content, and instead changes the encoding and decoding the original HTTP requests and responses, building an HTTP-tunnel over an existing XMPP connection.
 
This making it possible to move existing HTTP applications and move them into new settings 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 at your home) from your office without the need for a cloud service in-between.


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.


== Added URI ==
== Added URI ==
For this to work well there is a need for a new httpx:// [http://xmpp.org/extensions/xep-0332.html#sect-id129684 HTTPX uri scheme] which is easy for browsers to adopt


== How it works ==
== How it works ==
Jocke
16

edits

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

Navigation menu