Re: [Bluez-users] obex and d-bus (was permissions to set local name)

["Mikael Lindqvist" <li.mikael.spam@gmail.com>]

> > I have been looking a bit at openobex (I need it for another project)
> > and I would like to have it using non-blocking sockets when doing
> > connects. Would I be right in assuming that this would be needed if we
> > were to implement a dbus service for obex as well? Unless we want the
> > dbus-obex-daemon to be multi threaded, and that gives me strange
> > feelings in the stomach. At least that's not the way hcid is made,
> > i.e. it uses non blocking sockets when doing sdp connections, am I
> > right?
> >
> > I'm asking because I'm going to ask the openobex developers to accept
> > a patch which adds the possibility to use non blocking sockets for
> > connections (like sdp_lib can in bluez), and if I could say that it's
> > required for a d-bus service, it would add a bit of weight to my
> > arguments.
>
> you can use the FD transport of OpenOBEX for that and setup the RFCOMM
> non-blocking by yourself.
>

aha ok... yeps that works, just tried it... thanks!

-- Mikael

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users