I anticipate MG_EV_CLOSE to be delievered on every instance when TCP connection is terminated. If you can pinpoint the case when it's not like that, please report on how that can be reproduced.
On Mon, May 23, 2016 at 11:03 AM, Ake Hedman <[email protected]> wrote: > Sorry for that Sergey, > > I mean will MG_EV_CLOSE be issued after a web browser crash, page close > etc etc or are there scenarios when it will not be issued? I open a > session now when a socket is opened and close it when it is closed > (command) or when MG_EV_CLOSE is received. Still it looks like I get some > orphan sessions laying around some times. > > > On Monday, May 23, 2016 at 11:47:10 AM UTC+2, Sergey Lyubka wrote: >> >> >> Sorry Ake, I didn't get your question :-) >> > -- > You received this message because you are subscribed to the Google Groups > "mongoose-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/mongoose-users. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "mongoose-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/mongoose-users. For more options, visit https://groups.google.com/d/optout.
