From: Marcel Holtmann <marcel@holtmann.org>
To: suraj <suraj@atheros.com>
Cc: "linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
Jothikumar Mothilal <Jothikumar.Mothilal@Atheros.com>
Subject: Re: Sim Access profile server implementation
Date: Tue, 05 Oct 2010 10:02:10 +0200 [thread overview]
Message-ID: <1286265730.17473.29.camel@aeonflux> (raw)
In-Reply-To: <1285657515.12097.7.camel@atheros013-desktop>
Hi Suraj,
> Please find the Git tree for the Sim access profile server role
> implementation I have been working on at
>
> git://gitorious.org/sap-server/sap-server.git
>
> Not sure it could be directly used with Bluez. Nevertheless, it has the
> parser implementation of Bluetooth SAP packet. Someone could possibly
> reuse it in their implementation.
have you actually tested this with real SAP server capable hardware? I
am still not convinced at all to push APDU over D-Bus. First, there is
potential security issue here and second the latency that D-Bus
introduces seems not be acceptable. So what I am getting it, can this be
actually used in a product that seriously wants to support SAP server?
Regards
Marcel
next prev parent reply other threads:[~2010-10-05 8:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 7:05 Sim Access profile server implementation suraj
2010-10-05 8:02 ` Marcel Holtmann [this message]
2010-10-05 9:08 ` Suraj Sumangala
2010-10-05 10:45 ` Waldemar.Rymarkiewicz
2010-10-05 12:12 ` Marcel Holtmann
2010-10-05 12:46 ` Suraj Sumangala
2010-10-06 7:28 ` Waldemar.Rymarkiewicz
2010-10-06 9:32 ` Waldemar.Rymarkiewicz
2009-06-06 9:57 ` Suraj Sumangala
2010-10-06 10:13 ` Waldemar.Rymarkiewicz
2010-10-06 12:41 ` Suraj Sumangala
2010-10-06 13:22 ` Waldemar.Rymarkiewicz
2010-10-06 10:00 ` Suraj Sumangala
2010-10-07 15:42 ` Marcel Holtmann
2010-10-08 14:27 ` Waldemar.Rymarkiewicz
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=1286265730.17473.29.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=Jothikumar.Mothilal@Atheros.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=suraj@atheros.com \
/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