On Mon, Mar 14, 2011 at 20:58, Charlie Youakim <[email protected]> wrote: > Thank you for the response. I'll repost the question to XMPP.org, but I > think you've handled most of what I curious about. > My situation: > On the server side I have done nothing. It was a stock install of both > ejabberd and Openfire. On the client side it was as simple as pulling the > power on the client or switching off the wifi radio (there's a switch for > the radio on the two laptops I used). In all cases the user stayed > "Available". I can understand that this is difficult to fix, but one area I > think could be improved upon is this: After client1 was disconnected > (powered down) I messaged them through client2 (because the server still > told my client2 that client1 was "Available". At this point it would seem > to me that the server must attempt to send something to client1. Doesn't > the server see an error upon this send? If so, can't it automatically > adjust and say that client1 is now unavailable?
You are right by saying that the server must notify contacts if the server notices that a client has become unavailable. This is a XMPP requirement. Do you see this problem with the latest Vysper release? I know that we improved this area not too long ago. But maybe we didn't catch all cases. Bernd
