[jdev] XEP-0124 : polling meaning

[yasuharu...@nts.ricoh.co.jp]

Hi,

I want to ask you about the right definistion of "polling" in XEP-0124.

"polling" is written in 12.Polling Session below.

>> If a session will use "polling", the connection manager SHOULD specify a
higher than normal value for the 'inactivity' attribute in its session
creation response.
>> The increase SHOULD be greater than the value it specifies for the
'polling' attribute.

What "polling" mean?
I want to know when should I treat polling attribute of session creation
response.

"polling" means ,

(1) sending empty request to CM (long polling) ?

or

(2) setting the values of the 'wait' and/or 'hold' attributes in its
session creation request to "0",
and then "poll" the connection manager at regular intervals throughout the
session for payloads it might have received from the server ?

or

(3) something else ?

Sincerely,
Yasuharu

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

[Alexey Nezhdanov]

Usually there are two methods of staying in-sync:

polling and binding.

For binding client sends [empty] request to server and server does not reply until he have something to respond with (or until timeout expires)

For polling it is the same, just the server always replies instantly. So client have to poll over and over with some pre-defined interval.

I do not remember details about XMPP though so YMMV.

[Matthew Wild]

On 20 February 2012 10:41, <yasuharu...@nts.ricoh.co.jp> wrote:
> Hi,
>
> I want to ask you about the right definistion of "polling" in XEP-0124.
>
> "polling" is written in 12.Polling Session below.
>
>>> If a session will use "polling", the connection manager SHOULD specify a
> higher than normal value for the 'inactivity' attribute  in its session
> creation response.
>>> The increase SHOULD be greater than the value it specifies for the
> 'polling' attribute.
>
> What "polling" mean?
> I want to know when should I treat polling attribute of session creation
> response.
>
>
> "polling" means ,
>

>

> (2) setting the values of the 'wait' and/or 'hold' attributes in its
> session creation request to "0",
>  and then "poll" the connection manager at regular intervals throughout the
> session for payloads it might have received from the server ?
>

For your question, it means only this.

Regards,
Matthew

[yasuharu...@nts.ricoh.co.jp]

Thanks.

I understood what polling means.
If I don't do the 'polling', can I ignore 'polling' attribute of session
creation response ?

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.

[Alexander Gnauck]

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