From: Jean Tourrilhes <jt@bo...> - 2003-01-09 18:30:16
Ian Partridge wrote :
> How should a OBEX_CMD_DISCONNECT be handled? At the moment I cannot get my
> server to return to the idle state. After the OBEX_EV_REQDONE event is
> received from the OBEX_CMD_DISCONNECT command I am receiving a
> OBEX_EV_LINKERR event which is causing the server to fall out of it's
> OBEX_HandleInput() loop.
I think it's because the socket get closed. You could just
ignore the OBEX_EV_LINKERR if it comes *after* the OBEX_EV_REQDONE.
Note that the behaviour of OpenObex with respect to socket is
a bit weird at that point. I don't remember it, because in e-Squirt I
used the "accept" support which make things cleaner and more
straightforward in that respect. I would recommend to look at the
source code of an application that do work as you want and work from
Get latest updates about Open Source Projects, Conferences and News.