There are many different types of HTTP-based communication that one would like to be able to transport over XMPP. A non-exhaustive list can include:
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.
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.
1 Comment
Hanečák Peter