Difference between revisions of "Tech pages/IoT HttpOverXmpp"
Jump to navigation
Jump to search
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 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. | |||
== 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 == |