public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Using bluez-libs for non-blocking I/O
Date: Sun, 17 Jul 2005 15:30:31 +0200	[thread overview]
Message-ID: <1121607031.22662.4.camel@pegasus> (raw)
In-Reply-To: <9307f5f205071408293075bb92@mail.gmail.com>

Hi Paul,

> I've been digging the bluez mailing lists and the source code of the
> libraries for a while, but couldn't find a solution for my problem yet.
> I'm writing a bluetooth library in C++, it wraps the whole bluez-libs
> around C++ objects, I'll use it for my project of a GUI-based
> bluetooth management tool.
> Things have not been though until now, I've layed out the whole class
> hierarchy and most class member functions don't do anything but calling
> their bluez-counterpart.
> Now I wanted to implement an event-driven interface, using libsigc++
> to provide a basic callback mechanism (basically, the library gets a
> event from the hci device and dispatches it to the originating object
> trough the appropriate callback functor) but this is giving me quite
> some headaches, I'm going to have a single, separate, thread which
> does all the poll()ing stuff, I want to reuse as most of the original
> bluez library as possible, but I don't know how to make the existing
> hci_send_req() return immediately without waiting for a reply (which,
> in case of a asynchronous request, will be handled in the
> event-dispatching-thread described above), I don't want to rewrite
> hci_send_req() nor any of the many functions which rely on it, which
> could be the best solution ?

you need to use the raw HCI socket directly for this task. Examples on
how to do this have been posted to mailing list some time ago.

> Another question: the existing kernel modules and the library are able
> to handle multiple pending requests at once or am I just wasting my
> time trying to do something Bluez wasn't actually designed for ?

This depends on. For the same request, we handle it badly. For different
requests this should work.

Regards

Marcel




-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2005-07-17 13:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-14 15:29 [Bluez-devel] Using bluez-libs for non-blocking I/O P. Durante
2005-07-17 13:30 ` Marcel Holtmann [this message]

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=1121607031.22662.4.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox