[Standards] XMPP URI usage in "HTTP over XMPP"

Ralph Meijer ralphm at ik.nu
Wed Jul 10 20:51:55 UTC 2013

On 2013-07-10 22:27, Dave Cridland wrote:
>  > So, to be able to create such a seamless transition (which is also
> important in semantic web scenarios) we need an URI scheme that works in
> a syntactically identical manner as the already existing http URI
> scheme. Now, there exists another such URI scheme, which shows how this
> is best done: the https URI scheme. Basically it's the same problem: How
> to create a new transport of HTTP messages, but maintaining URI syntax
> logic available in clients.
> I wonder, though, what other options would satisfy.
> Given http://example.org/, could we have a browser which understood
> HTTP/XMPP transition seamlessly to fetching from an XMPP entity instead?
> Also, my impression based around a quick read rather than detailed
> review is that this is a simple mapping of HTTP/1.1 to an XMPP
> transport; I wonder if this should be examined in the light of the
> advances present in HTTP/2.0 (AKA SPDY).

Do you mean just using XMPP as the actual protocol dereferencing normal 
http(s) URIs? Interesting thought.


More information about the Standards mailing list