[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jabber-jdev
Subject:    Re: [jdev] XEP-0124 : polling meaning
From:       Alexander Gnauck <gnauck () ag-software ! de>
Date:       2012-02-21 11:19:44
Message-ID: CAGwkmH1mdfn5zDd4KOv45+kHOkhUMaOd0V69ssCQQtUD1R9=JA () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


> But in Overactivity section,  It seems that client needs to watch 'polling'
> attribute to avoid overactivity.
>
> http://xmpp.org/extensions/xep-0124.html#overactive
> Quote:
> 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.

Alex

[Attachment #5 (text/html)]

<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex">But in Overactivity section,  It \
seems that client needs to watch &#39;polling&#39;<br> attribute to avoid \
overactivity.<br> <br>
<a href="http://xmpp.org/extensions/xep-0124.html#overactive" \
target="_blank">http://xmpp.org/extensions/xep-0124.html#overactive</a><br> \
Quote:<br> If during any period the client sends a sequence of new requests equal \
in<br> length to the number specified by the &#39;requests&#39; attribute, and if \
the<br> connection manager has not yet responded to any of the  requests, and if<br>
the last request was empty and did not include either a &#39;pause&#39; attribute<br>
or a &#39;type&#39; attribute set to &quot;terminate&quot;, and if the last two \
requests<br> arrived within a period shorter than the number of seconds specified by \
the<br> &#39;polling&#39; attribute in the session creation response, then the \
connection<br> manager SHOULD consider that the client is making requests more \
frequently<br> than it was permitted and terminate the HTTP session and return a<br>
&#39;policy-violation&#39; terminal binding error to the client. Note: the \
behavior<br> for Polling Sessions is slightly \
different.<br><br></blockquote><div>geez, had to read this long sentence about 10 \
times to understand it ;-).</div><div><br></div><div>Strictly speaking I would say \
yes. This client should avoid overactivity also in binding mode.</div>

<div>In practice this makes not much sense to me, and I have not seen any servers \
enforcing this rule.</div><div>Openfire seems to enforce this when the client or \
proxy in between supports no keep alives.</div><div><br></div>

<div>Alex</div></div>



_______________________________________________
JDev mailing list
Info: http://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: JDev-unsubscribe@jabber.org
_______________________________________________


[prev in list] [next in list] [prev in thread] [next in thread]