From: Johan Hedberg <johan.hedberg@gmail.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [BlueZ-Announce] Release of bluez-libs-3.30 and bluez-utils-3.30
Date: Thu, 3 Apr 2008 23:53:40 +0300 [thread overview]
Message-ID: <CDC3B7EE-50E8-409A-8F70-D98CC13018A5@gmail.com> (raw)
In-Reply-To: <e29894ca0804031337n1b68f8c3j9ce3f16fe4867904@mail.gmail.com>
On Apr 3, 2008, at 23:37, Marc-Andr=E9 Lureau wrote:
>
> On Thu, Apr 3, 2008 at 10:54 PM, Marcel Holtmann =
> <marcel@holtmann.org> wrote:
>>
>> After a long discussion, the consensus was to use plugins instead of
>> separate processes for the future of BlueZ. This release marks the =
>> start
>> of this change. All existing services have been converted to plugins
>> while keeping the old D-Bus API.
>
> I am just being curious, I'd like to know why the separate processes
> approach was dropped.
It isn't of course the whole story (Marcel will probably fill up with =
more reasons), but the following is a table of the pros/cons of each =
approach that we created couple of weeks ago when planing the 4.x =
work: http://iki.fi/jhedberg/plugin-vs-process.jpg
Johan
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2008-04-03 20:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1207252447.18442.11.camel@californication>
2008-04-03 20:37 ` [Bluez-devel] [BlueZ-Announce] Release of bluez-libs-3.30 and bluez-utils-3.30 Marc-André Lureau
2008-04-03 20:53 ` Johan Hedberg [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=CDC3B7EE-50E8-409A-8F70-D98CC13018A5@gmail.com \
--to=johan.hedberg@gmail.com \
--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