Quoting Vinod Panicker <[EMAIL PROTECTED]>:
Yes, thats exactly what I'm talking about.  But I dont see any mention
of "how" and "when" to do this in the RFC.  Also, you mentioned that
the server "should" send it after receiving initial presence from the
user - not "must"?

Well, I don't really have a habit of using RFC-speek in emails.

Here's the relevant information from RFC 3921, anyway.

Section 5.1.1  Initial Presence:
Upon receiving initial presence from a client, the user's server MUST do the
following if there is not already one or more available resources for the
user (if there is already one or more available resources for the user, the
server obviously does not need to send the presence probes, since it already
possesses the requisite information):
   1. Send presence probes...<snipped because it's pretty long>

To summarise: after you send the initial presence, the server MUST send presence
probes to all contacts.

Section 5.1.3  Presence Probes:
Upon receiving a presence probe from the user, the contact's server SHOULD
reply as follows:
<snip>
   4. Else, if the contact has at least one available resource, the server
      MUST reply to the presence probe by sending to the user the full XML of
      the last presence stanza with no 'to' attribute received by the server
      from each of the contact's available resources (again, subject to
      privacy lists in force for each session).

To summarise: after your server sends a probe to the other contact's server,
that server MUST reply by sending *you* the full XML of the last presence
stanzas.

Add the two together, and you'll see that the flood has to occur immediately
after you send your own one out.

And what abt this restriction on not being able to
see contacts' presence before sending own initial presence?

This much is plain commonsense.  If your contact's server doesn't even know
you're online, it can't know you're there to send the presence to, let alone
know when to send it. :-)

TX


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

_______________________________________________
jdev mailing list
[email protected]
http://mail.jabber.org/mailman/listinfo/jdev

Reply via email to