On Mon, Mar 8, 2010 at 20:34, Bernd Fondermann <[email protected]> wrote: > Thomas Kratz wrote: >> Hi all, >> >> I don't know if my question yesterday was concrete enough. >> >> I try to send an unavailable message when the connection breaks down >> and I wonder if I can somehow wait for the message to go out. > > Wait a second. > > There are different cases: > > a. Client sends <pres unavail.../> and keeps connection alive > b. Client sends <pres unavail.../> (maybe followed by a </stream:stream> > and closes the socket > c. Client dies, Routing is broken, Socket cannot transport packets > successfully end-to-end and the server detects this, because the socket > gets closed - this is without the client notifying the server of anything > d. Server goes down and is in process of ending all sessions > > Up until now, I thought we were talking c., right? > a. is (should be) already working > b. is not fully working, but we would be working on the wrong end then > d. must be handled completely different. > > So, what is/are your case(s)? > >> Because >> afterwards the session gets CLOSED and an unbind happens, which now >> makes my attempt to send the unavailable break. > >> Or is there a way to >> send a Stanza synchronuosly? > > in MinaBackedSessionContext there is write(Stanza). This is a hack. So > is everything attached to VYSPER-185.
On the not-a-hack front I changed the endSession() signature. It now receives a hint what causes the termination. Bernd
