Matthew Wild wrote:
On Wed, Aug 6, 2008 at 8:55 PM, Tobias Markmann <[EMAIL PROTECTED]> wrote:Hi,Okay, here some questions to make this ML look like it's actively used. ;) What is the suggested value for the 'hold' attribute in a session creation request?1If any value fits, why is the existence of the 'hold' attribute a SHOULD?" 'hold' -- This attribute specifies the maximum number of requests the connection manager is allowed to keep waiting at any one time during the session. If the client is not able to use HTTP Pipelining then this SHOULD be set to "1". " I agree that the text is confusing regarding pipelining support. The truth is that you don't know if you can use pipelining until you try it. Even if it is supported by the BOSH CM then it may not be by some proxy in-between. I believe the best you can do is set hold to 1, and try pipelining. If it doesn't work (server returns HTTP 1.0 or connection:close) then you can degrade gracefully to using multiple connections. This is what I made gloox do.
I've added an implementation note to this effect. Peter
smime.p7s
Description: S/MIME Cryptographic Signature
