Hello Sergey There are many aims in fact.
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. 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. 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?). 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. Sincerely, Peter Waher -----Original Message----- From: Sergey Dobrov [mailto:[email protected]] Sent: den 16 maj 2013 06:05 To: XMPP Standards Subject: Re: [Standards] Proposed XMPP Extension: HTTP over XMPP transport I have tried to read the introduction carefully, but I didn't get the aim of the XEP. Why do we need it exactly? I was dreaming about using XMPP as a new web protocol but I didn't think about it as a porting old HTTP protocol with it's problems to XMPP entirely... So, if someone will be so kind to express his thoughts about how this protocol can be useful, I would very appreciate. Thanks. On 05/07/2013 09:07 PM, XMPP Extensions Editor wrote: > The XMPP Extensions Editor has received a proposal for a new XEP. > > Title: HTTP over XMPP transport > > Abstract: This specification defines how XMPP can be used to transport HTTP > communication over peer-to-peer networks. > > URL: http://xmpp.org/extensions/inbox/http-over-xmpp.html > > The XMPP Council will decide in the next two weeks whether to accept this > proposal as an official XEP. > > -- With best regards, Sergey Dobrov, XMPP Developer and JRuDevels.org founder.
