-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ian Paterson wrote:
>> Peter wrote:
>>> *Some runtime environments constrain the
number of simultaneous HTTP
>>> requests a client may make to each connection
manager; if such clients
>>> need to connect using more than one account at
the same time, then
>>> support for multi-stream sessions is essential.
>>>
>>> * While XMPP does not allow two sessions
with the same full JID to
>>> be open at the same time, it does use one
stream in each direction for
>>> client-to-server connections; support for
multiple streams enables
>>> clients that connect via the HTTP Binding to
emulate that behavior and
>>> thereby reduce network traffic.
>
> I don't understand this second point (even if I assume
that
> 'server-to-server' was meant instead of
'client-to-server').
>
> The intention of the original text was simply to say
that restricted
> clients *need* multi-streams if they want to open more
than one XMPP
> stream (with different JIDs). Other entities might not
need to support
> multi-stream sessions in these cases (they could open
multiple sessions
> instead), but it would be much more efficient for them
to employ
> multi-stream sessions. (Since with multi-stream
sessions only one HTTP
> request to the server is necessary to service all the
streams in the
> session.)
Does the following text (to replace the second bullet point)
capture the
intent, or shall we simply remove the second bullet point
entirely?
***
While XMPP does not allow two sessions with the same full
JID to be open
at the same time, some entities that use an HTTP Binding
connection
manager may want to manage streams for multiple sessions at
once (e.g.,
certain kinds of web clients); support for multiple streams
makes this
possible and also enables clients to reduce network traffic.
***
Thanks.
Peter
- --
Peter Saint-Andre
Jabber Software Foundation
http://www
.jabber.org/people/stpeter.shtml
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEUkEkNF1RSzyt3NURAiD/AKDmB5P5b4UXkvUxe96nTRGqMWT+QQCg
66A6
emdBof3yIT+Iai5vnU/JlVU=
=R3hV
-----END PGP SIGNATURE-----
|