From: Claudio Takahasi <cktakahasi@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] bluetoothd D-Bus interface proposals(draft 00.05)
Date: Tue, 16 Aug 2005 18:15:37 -0300 [thread overview]
Message-ID: <e1effdeb05081614151ee4f4bd@mail.gmail.com> (raw)
Hi folks,
I am posting a new draft of D-Bus architecture and Interfaces.=20
If someone has comments regarding the design, interfaces or any kind
of question send us a feedback.
This last draft contains some changes based on Johan Hedberg feedback
and new services.
Major changes:
* Return "D-Bus error messages" instead of "method return" following
the Johan Hedberg suggestion
* Defined standard error messages
* Added "architecture" overview section.
* Using just one interface for request and signals instead of distinct
interfaces. The message type can be discovered using the message type
attribute embedded in the D-Bus message header.
Location:
The document (draft 00.05) can be found at: http://www.cin.ufpe.br/~ckt/blu=
ez
Next action:
* define SDP D-Bus services and architecture.
* Multi-level disconnection/connection signals. Is it really
necessary? eg: send disconnect signal at pan and hci D-Bus interfaces.
* Signal level. Is it possible check it? IS it really necessary?
* Unify rfcomm and dun D-Bus services. Is it feasible?
Suggestions a welcome!
Regards,
Claudio
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2005-08-16 21:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-16 21:15 Claudio Takahasi [this message]
2005-08-16 22:45 ` [Bluez-devel] bluetoothd D-Bus interface proposals(draft 00.05) P. Durante
2005-08-18 12:05 ` Claudio Takahasi
2005-08-18 20:58 ` P. Durante
2005-08-19 17:27 ` Elvis Pfützenreuter
2005-08-22 11:17 ` Marcel Holtmann
2005-08-22 12:04 ` Elvis Pfützenreuter
2005-08-22 12:27 ` Claudio Takahasi
2005-08-22 12:37 ` Peter Robinson
2005-08-22 12:51 ` Claudio Takahasi
2005-08-22 14:26 ` P. Durante
2005-08-22 14:34 ` Marcel Holtmann
2005-08-22 17:39 ` Claudio Takahasi
2005-08-22 17:50 ` Marcel Holtmann
2005-08-22 19:47 ` Claudio Takahasi
2005-08-29 21:13 ` Claudio Takahasi
2005-08-29 21:46 ` Marcel Holtmann
2005-08-30 10:07 ` Paul Hedderly
2005-08-30 13:14 ` Claudio Takahasi
2005-08-30 18:16 ` Claudio Takahasi
2005-09-01 9:57 ` Marcel Holtmann
2005-08-22 14:29 ` Marcel Holtmann
2005-08-22 14:27 ` Marcel Holtmann
2005-08-22 14:21 ` Marcel Holtmann
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=e1effdeb05081614151ee4f4bd@mail.gmail.com \
--to=cktakahasi@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 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.