From: Hendrik S. <po...@he...> - 2008-03-25 12:54:41
|
Am Dienstag 25 März 2008 schrieb Nick Bransby-Williams: > My obex_event_t callback function is never called as the transport > fails to connect and I dont end up sending any requests. OK. > > 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.? Not when you stick to the API. OTOH, when BtOBEX_TransportConnect() returns with -1, you can ask "errno", don't you? I must admit, though, that the API lacks there. HS |