From: "Collin R. Mulliner" <collin@betaversion.net>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Many simultaneous BtOBEX_TransportConnect ?
Date: Fri, 21 Jul 2006 00:02:01 +0200 [thread overview]
Message-ID: <1153432921.23838.27.camel@panic> (raw)
In-Reply-To: <4688DDA1-7466-48A2-A968-1636CE3E4C50@infitsrl.com>
I think this is a OpenOBEX limitation, the workaround is to create the
rfcomm connections "by hand" and then use the OpenOBEX file descriptor
interface.
...
context.libObex = OBEX_Init(OBEX_TRANS_FD, eventhandler, 0);
...
FdOBEX_TransportSetup(...)
...
Collin
On Thu, 2006-07-20 at 22:36 +0200, Fabrizio Guglielmino wrote:
> I'm facing a problem with bluez and I can't found the solution.
> Situation is:
> bluez-libs-3.1
> openobex-1.2
> linux kernel 2.6.12
>
> I'm simply trying to send a file (vcard) to two cellular phones
> simultaneous using object push profile.
> I've writed a little C program based on obex_test that take btaddr,
> channel and filename and push the last.
> If I send to only one device all it'ok, but if I try to send
> simultaneous launcing two commands in cascade the first go ok but the
> second
> always fail in BtOBEX_TransportConnect of openobex ibrary.
>
> Testing two rfcomm connection to same devices all works....
>
> Is this a bluez (or openopex) limitation?
>
> I've implemented the same on windows xp with microsoft stack without
> problems and
> I'm testing the solutions with the same bluetooth usd dongles.
>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
--
Collin R. Mulliner <collin@betaversion.net>
BETAVERSiON Systems [www.betaversion.net]
info/pgp: finger collin@betaversion.net
He is dead Jim! --Dr. McCoy
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-07-20 22:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-20 20:36 [Bluez-devel] Many simultaneous BtOBEX_TransportConnect ? Fabrizio Guglielmino
2006-07-20 22:02 ` Collin R. Mulliner [this message]
2006-07-26 7:22 ` Marcel Holtmann
2006-07-26 15:17 ` Fabrizio Guglielmino
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=1153432921.23838.27.camel@panic \
--to=collin@betaversion.net \
--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;
as well as URLs for NNTP newsgroup(s).