On 25/03/2008, Hendrik Sattler <[EMAIL PROTECTED]> wrote: > Am Dienstag 25 März 2008 schrieb Nick Bransby-Williams: > > > When pushing files to mobile via OPP, I need to find out if a user > > refused the connection (via the on screen prompt 'Accept Message > > from...') or the connection just timed out. > > > > Thing is, BtOBEX_TransportConnect blocks while the phone displays the > > prompt and then returns with either -1 or 1 (success or failure) > > leaving me with no way to access the actual response from the phone. > > > > I thought it would a case of reading the response from the obex > > connect command request but this all happens before i send the connect > > request (unless BtOBEX_TransportConnect is sending one for me?) > > > > Any ideas? > > > Use the last variable in your obex_event_t callback function when the event is > OBEX_EV_ABORT?
My obex_event_t callback function is never called as the transport fails to connect and I dont end up sending any requests. > OTOH, at that time of connection establishment, the connection should _never_ > timeout! Don't force the user to be quick, react to disconnection instead. I dont timeout the connection - the phone does! If i was timing out the connection then i could work out if it was the disconnection timed out or was refused. Is there a connecting the transport manually without BtOBEX_TransportConnect? Is it possible to the Bluez D-BUS API to setup a RFCOMM connection and then pass the resulting socket to openobex.? ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Openobex-users mailing list [email protected] http://lists.sourceforge.net/lists/listinfo/openobex-users
