From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] obex and d-bus (was permissions to set local name)
Date: Tue, 21 Nov 2006 15:40:26 +0100 [thread overview]
Message-ID: <1164120026.28429.37.camel@localhost> (raw)
In-Reply-To: <b5dccebe0611210636l574f6e67y204c613e780e302f@mail.gmail.com>
Hi Mikael,
> 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.
Regards
Marcel
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2006-11-21 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-21 14:36 [Bluez-users] obex and d-bus (was permissions to set local name) Mikael Lindqvist
2006-11-21 14:40 ` Marcel Holtmann [this message]
2006-11-21 15:08 ` Mikael Lindqvist
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1164120026.28429.37.camel@localhost \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.