15
edits
Difference between revisions of "Tech pages/IoT HttpOverXmpp"
Jump to navigation
Jump to search
Tech pages/IoT HttpOverXmpp (view source)
Revision as of 17:49, 1 November 2013
, 17:49, 1 November 2013→Layout
PeterWaher (talk | contribs) (→Layout) |
|||
| (2 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
= Layout= | = Layout = | ||
{{XmppIoTLayout}} | |||
== Introduction == | == Introduction == | ||
| Line 15: | Line 8: | ||
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. | 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. | 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. | ||
| Line 20: | Line 14: | ||
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. | 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. | ||
There are many different types of HTTP-based communication that could be transported | There are many different types of HTTP-based communication that could be transported | ||
| Line 31: | Line 24: | ||
* Streamed multi-media content in UPnP and DLNA networks. | * Streamed multi-media content in UPnP and DLNA networks. | ||
But instead of looking at all possible HTTP transports and make them transportable over XMPP like [http://xmpp.org/extensions/xep-0072.html | XEP-0072 SOAP 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. | |||
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 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. | ||
| Line 38: | Line 30: | ||
== Added URI == | == Added URI == | ||
For this to work well there is a need for a new httpx:// [http://xmpp.org/extensions/xep-0332.html# | For this to work well there is a need for a new httpx:// [http://xmpp.org/extensions/xep-0332.html#httpxscheme HTTPX uri scheme] which is easy for browsers to adopt | ||
== | == Examples == | ||