[jdev] XEP-0124 : polling meaning
gnauck at ag-software.de
Tue Feb 21 11:19:44 UTC 2012
> But in Overactivity section, It seems that client needs to watch 'polling'
> attribute to avoid overactivity.
> If during any period the client sends a sequence of new requests equal in
> length to the number specified by the 'requests' attribute, and if the
> connection manager has not yet responded to any of the requests, and if
> the last request was empty and did not include either a 'pause' attribute
> or a 'type' attribute set to "terminate", and if the last two requests
> arrived within a period shorter than the number of seconds specified by the
> 'polling' attribute in the session creation response, then the connection
> manager SHOULD consider that the client is making requests more frequently
> than it was permitted and terminate the HTTP session and return a
> 'policy-violation' terminal binding error to the client. Note: the behavior
> for Polling Sessions is slightly different.
> geez, had to read this long sentence about 10 times to understand it ;-).
Strictly speaking I would say yes. This client should avoid overactivity
also in binding mode.
In practice this makes not much sense to me, and I have not seen any
servers enforcing this rule.
Openfire seems to enforce this when the client or proxy in between supports
no keep alives.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the JDev