On Thu, Mar 19, 2009 at 11:27 PM, Justin Karneges
<[email protected]> wrote:
> It's also useful to ping the connection when there's otherwise no traffic. Of
> course you could just use the ack packets with a sequence number for this,
> but having a separate <ping> element seemed cleaner.
but compressors like little entropy ;)
>> I'm asking
> Indeed, which is why the original document said the server SHOULD respond to
> pings while throttling, not that it MUST. However, maybe it's time to
> reevaluate how throttling should be done.
Yes, but things bound to timeouts are more difficult ti handle
> In order to ensure presence isn't stale, clients (and servers) are going to
> want to abandon the connection quickly if it appears dead. I understand that
> not reading the socket is a very good way to throttle connections, but at the
> same time how is a client supposed to tell the difference between a throttled
> connection and a dead connection? Maybe the server could send unsolicited
> pongs ("you're not dead!") while the receive channel is blocked?
I was thinking exactly to this, something sent by the server in order
to tell "please slow down". Pongs are perfect candidates
bye
--
Fabio Forno, Ph.D.
Bluendo srl http://www.bluendo.com
jabber id: [email protected]
