On 2009/07/15, at 15:53, Remko Tronçon wrote:
work for me, as it takes 5 minutes until I see all presences (which
SUCKS!).
Sounds like you have a much bigger problem then. If your server takes
5 minutes to process all presence from your contacts, it means your
initial roster get with your schema will take 5 minutes as well, so
you won't be able to IM *at all* during that period.
I really don't see the problem with presence flood. Any presence you
get as a <presence/> stanza will have to be in your initial roster get
too, which means that your initial roster will be a huge stanza
(possibly exceeding server and client limits), and you'll lose all the
advantages of asynchronous roster building (i.e. your client will have
to block until your server is ready).
+1.
Really, regarding presence flood, I don't find that a problem at all,
and mixing presence with roster is a mistake IMHO. The two concepts
are related but not the same (think about direct presence management.
You don't have to have a roster entry with someone to exchange
presence information with it). So tieing "presence" information to
"roster" information in your client will limit you in the long run.
I do agree that servers could be a bit smarter and keep track of the
latest presence for you so that most if not all of the "last" presence
stanzas would be available upon connect, without having to wait for
probe responses.
But thats a server optimization.
Best regards,
