On 12/12/05, <b class="gmail_sendername">Nicolas Niclausse</b> <<a href="mailto:firstname.lastname@example.org">email@example.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Jason Tucker a écrit :<br>> On 12/9/05, *Nicolas Niclausse* <<a href="mailto:firstname.lastname@example.org">email@example.com</a><br>> <mailto:<a href="mailto:firstname.lastname@example.org">email@example.com</a>>> wrote:<br>
><br>><br>> Yes, a user is considered online as soon as he is connected, so it's<br>> possible to get an offline message in the case you describe.<br>><br>><br>> Is there any way this behavior can be altered? It would be *much* better
<br>> if tsunami only considered a user online after they have authenticated.<br><br>Is it after authentication or after the "presence" msg is received by<br>the server ?</blockquote><div><br>After authentication. During the last part of the authentication phase, the client sends an jabber:iq:auth 'set' mesage to the server. Assuming successful authentication, the server would respond with an iq type='result'. At this point the client session is fully established - any messages sent to this client prior to this point will go to offline message store.
<br><br>For my purposes, it would be ideal if there was a way to put this in the idx-tsunami.xml as a configurable element. This part of the tsunami code is well beyond my skills, though, or I'd try to contribute something.
<br><br>While we're on the subject, would you have any idea why at around 25,600 (approximately) we would start running into problems with messages sent to online users? The test starts off OK (sometimes sporadic offline messages due to the problem we've discussed), but basically goes well until about ~25.6K users. Then suddenly, like clockwork, tsunami starts hitting *recently* connected users with messages - before they have a chance to auth. I don't know how tsunami stores the list of online users, or how it then selects an online user to send a message to... but it is very odd that it always happens at this point.
<br><br>Anyway - if the first problem could be fixed (onlline only if authed), then the second part of my problem would probably be irrelevant.<br><br>__Jason<br></div><br></div><br>