public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Vikas Sinha" <compuvikas@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Obex handle?
Date: Thu, 19 Jul 2007 10:09:07 +0530	[thread overview]
Message-ID: <1ab01fb50707182139y7e3798bej80dd486f23140d8b@mail.gmail.com> (raw)
In-Reply-To: <200707181232.00253.fernando@bluexare.org>


[-- Attachment #1.1: Type: text/plain, Size: 1652 bytes --]

Go and check mailing list .. Few months ago someone asked same question.
http://blog.gmane.org/gmane.linux.bluez.devel/month=20070501


well i don't know about DBUS but with obex and hci layer I have controlled
multiple  Dongles.
You can find solution here



On 7/18/07, Fernando Unzu <fernando@bluexare.org> wrote:
>
> Hello,
>
> I have a question about how to select which device I want to use with my
> program.
>
> I have an application that sends some content t another bluetooth devices,
> and
> i realize the transfer with Obex functions.
>
> But if I have two dongles in my PC, I would can to select between one and
> other.
> This is what i don't know how to do.
>
> The handle is created with Obex_Init, and I think it is in that moment
> when I
> select one of the dongles, but I don't know how.
>
> Or there is another way to do it?? Or it has to be done in another moment
> with
> another function??
>
> I have eard that DBus solves this problems...; anybody can help me,
> please?
>
> P.D.: Although anybody gives me a DBus solution, I'm interesting in the
> Obex
> solution too.
>
> Thank you,
> Fernando Unzu
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>



-- 
Impossible
itself contain
I M Possible

Vikas

[-- Attachment #1.2: Type: text/html, Size: 2589 bytes --]

[-- Attachment #2: Type: text/plain, Size: 286 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2007-07-19  4:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-18 10:32 [Bluez-devel] Obex handle? Fernando Unzu
2007-07-19  4:39 ` Vikas Sinha [this message]
2007-07-19  4:44   ` [Bluez-devel] Inquiry Response tjoconno
2007-07-19 10:16   ` [Bluez-devel] Obex handle? Fernando Unzu
2007-07-19 13:11     ` Manuel Naranjo
2007-07-23 11:06       ` Fernando Unzu

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=1ab01fb50707182139y7e3798bej80dd486f23140d8b@mail.gmail.com \
    --to=compuvikas@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