<html><head></head><body><div>"4. The BOSH Technique" says:</div><div><br></div><div>"If the client has data to send while a request is still open, it establishes a second socket connection to the connection manager to send a new request. The connection manager immediately responds to the previously held request (possibly with no data) and holds open this new request. This results in the connections switching roles; the "old" connection is responded to and left awaiting new requests, while the "new" connection is now used for the long polling loop."</div><div><br></div><div>So if you know that there are other messages pending at the client, do not use hold/wait until your sending queue is empty. If during a hold, the client needs to send a new message, open/reuse the secondary connection, if it needs to be sent before the wait interval has expired.</div><div><br></div><div>-Marcel</div><div><br></div><div>On Fre, 2016-07-01 at 15:46 +0530, Vaibhav Ranglani wrote:</div><blockquote type="cite"><div dir="ltr"><div><div><div>Hello devs,<br><br></div>I am implementing a custom solution in XMPP.<br><br></div>During the session creation request, the client sends a session creation request as follows.<br><br></div><div><pre class=""><span class=""><</span><span class="">body content</span><span class="">=</span><span class="">'text/xml; charset=utf-8'</span><span class=""><br> </span><span class="">from</span><span class="">=</span><span class="">'<a href="mailto:user@example.com">user@example.com</a>'</span><span class=""><br> hold</span><span class="">=</span><span class="">'1'</span><span class=""><br> rid</span><span class="">=</span><span class="">'1573741820'</span><span class=""><br> to</span><span class="">=</span><span class="">'<a href="http://example.com">example.com</a>'</span><span class=""><br> route</span><span class="">=</span><span class="">'xmpp:<a href="http://example.com:9999">example.com:9999</a>'</span><span class=""><br> ver</span><span class="">=</span><span class="">'1.6'</span><span class=""><br> wait</span><span class="">=</span><span class="">'60'</span><span class=""><br> ack</span><span class="">=</span><span class="">'1'</span><span class=""><br> xml</span><span class="">:</span><span class="">lang</span><span class="">=</span><span class="">'en'</span><span class=""><br> xmlns</span><span class="">=</span><span class="">'<a href="http://jabber.org/protocol/httpbind">http://jabber.org/protocol/httpbind</a>'</span><span class="">/><br><br></span><br><span style="font-family:arial,helvetica,sans-serif">In this request, the hold attribute is specified as 1. <br>Due to this the issue I am encountering is that I am able to send only 1 message per minute.<br><br></span></pre><pre class=""><span style="font-family:arial,helvetica,sans-serif">Can I specify a value of 30-40 for hold variable. If yes, then what will be the performance ramifications of this?<br><br></span></pre><pre class=""><span style="font-family:arial,helvetica,sans-serif">Regards<br>Vaibhav<br></span></pre></div></div> <pre>_______________________________________________ JDev mailing list Info: <a href="http://mail.jabber.org/mailman/listinfo/jdev">http://mail.jabber.org/mailman/listinfo/jdev</a> Unsubscribe: <a href="mailto:JDev-unsubscribe@jabber.org">JDev-unsubscribe@jabber.org</a> _______________________________________________ </pre></blockquote></body></html>