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. Am 20. Februar 2012 11:41 schrieb <[email protected]>: > 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: [email protected] > _______________________________________________ >
_______________________________________________ JDev mailing list Info: http://mail.jabber.org/mailman/listinfo/jdev Unsubscribe: [email protected] _______________________________________________
