[Standards] UPDATED: XEP-0332 (HTTP over XMPP transport)
Peter.Waher at clayster.com
Thu Aug 21 15:01:51 UTC 2014
Thanks for your comment. Just wanted to point out the possibility as such, even though it would probably not be used by the web server. Since content is normally returned based on query parameters and request headers, the actual content selection would probably be made by the underlying web server, and it would return the corresponding stream. But since there are formats including multiple streams, my thought was to point out the possibility of using this fact, as a possibility to optimize performance in such cases.
What do you refer to, when you say the "new jingly-pub stuff"?
From: Philipp Hancke [mailto:fippo at goodadvice.pages.de]
Sent: den 21 augusti 2014 07:58
To: standards at xmpp.org
Subject: Re: [Standards] UPDATED: XEP-0332 (HTTP over XMPP transport)
Am 13.08.2014 18:12, schrieb XMPP Extensions Editor:
> Version 0.3 of XEP-0332 (HTTP over XMPP transport) has been released.
> Abstract: This specification defines how XMPP can be used to transport HTTP communication over peer-to-peer networks.
> Changelog: [See revision history] (pw)
> Diff: http://xmpp.org/extensions/diff/api/xep/0332/diff/0.2/vs/0.3
> URL: http://xmpp.org/extensions/xep-0332.html
one thing I noticed:
Using Jingle in this way makes it possible for an intelligent
server to return multiple streams the client can choose from,
something that is not done in normal HTTP over TCP. The first
candidate should however correspond to the same stream that
would have been returned if the request had been made using
normal HTTP over TCP.
That is not how candidates or ice work. You want either multiple contents or the new jingle-pub stuff.
More information about the Standards