2009/7/17 Pedro Melo <[email protected]>: > Hi, > > On 2009/07/16, at 14:14, Jiří Zárevúcky wrote: > >> I think there is one way to really solve the issue in question. >> >> As I understand it, the problem is that when user logs it, he doesn't >> know whether the contact is online or not. Sending all presences >> together is not an option, as it would require waiting for all the >> probes to respond. >> >> Now, I'm not exactly sure how this works with server implementations, >> but my guess is that the once the s2s connection is established (which >> can vary widely for every server) all the probes (should) get >> processed and returned in a relatively short timespan. >> >> What we need to do, is to make client aware that he has received all >> the delayed presences from a particular domain. >> It would then be possible to display contacts with some sort of >> "waiting" state, so the user knows whether the contact in question is >> offline, or the s2s connection just didn't get through yet. >> >> All in all, this could be very simply defined in a short XEP. > > Several people pointed out that this problem is already solved with > jabber::delay. So far you didn't seem to acknowledge it either positively > ("yes it might solve the problem") or negatively ("no it doesn't solve the > problem because of X, Y and Z"). > > Before start Yet Another XEP, can you tell me why do you think that > jabber:x:delay is not an option? > > Thanks in advance,
Several people lack the understanding of the problem Jonathan was trying to solve. The original problem is that when you connect, you see everyone offline. Even if they are online, you may have to wait several minutes to see it under some circumstances. If you connect just to quicky check someone's availability, you have a problem, because you can't be entirely sure of him *not* being available unless you actually open an XML console of your client and send a probe yourself (and that only for some implementations anyway). Delay only solves the problem of distinguishing delayed and live presences. The way it works now can be lived with, but I've stumbled several times over this particular problem (as a user) and even though it doesn't affect me often, it's very annoying when it does. As a side note, jabber:x:delay is not an option because it's obsolete. ;-)
