From: Ian Partridge <iop199@ec...> - 2003-01-08 12:32:11
I am trying to write a simple server application (running over Bluetooth)
to send files between two TDK Bluetooth dongles (one of which will be
running the server, and the other a simple client application).
As this is only between two machines, I am not interested in the server
being able to handle multiple incoming connections simultaneously -- the
client will merely issue OBEX_CMD_CONNECT, OBEX_CMD_GET, and
OBEX_CMD_DISCONNECT (in that order) repeatedly. When an
OBEX_CMD_DISCONNECT is received the server should return to it's idle loop
ready for the next OBEX_CMD_CONNECT to be received.
My question is this:
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
This occurs whether or not I disconnect the transport in the
Can anyone advise? If seeing my source code would help, just ask.
Many thanks in advance,