From: Fabrizio Guglielmino <guglielmino@infitsrl.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Scan and push images
Date: Tue, 27 Nov 2007 12:13:57 +0100 [thread overview]
Message-ID: <474BFBF5.50500@infitsrl.com> (raw)
In-Reply-To: <1196161587.17196.37.camel@aeonflux>
Marcel Holtmann ha scritto:
> Hi Fabrizio,
>
>
>> Ok for the subject, excuse me.
>>
>
> and please inline response. Otherwise it is hard to follow.
>
>
>> I can't undertand "You are simply blocking the baseband with your random
>> attempts", where are the random attemps?
>> One thread is dedicated to make inquiry, it bind on a specific local
>> adapter and make an infinite loop of inquiry (with a parametric sleep on
>> every iteration).
>>
>> On the other side for every device discovered it's lauched a thread for
>> these operations:
>> 1) sdp query for OPUSH service (serialized with a mutex)
>> 2) connection to eventually discovered RFCOMM channel of the object push
>> service
>> 3) push of the content (with my own working obex implementation)
>>
>
> as long as you only have one adapter attached to your system, you have
> attempts to run inquiry and paging at the same time. This is not working
> out. You can only do one thing at a time.
>
Yes but I'm using two adapters so It's not a problem...
>
>> I'd like to accept Your suggests but:
>> - If I use periodic inquiry I need obligatory dbus to receive callback
>> events?
>>
>
> You can do it by hand on a raw socket, but why would you? D-Bus gives it
> to you nicely.
>
Ok, I've to look about using dbus in plain C because I don't want to use
Glib.
>
>> - How can I perform pre-filter on remote devices that support object
>> transfer if I've not discovered their servies?
>>
>
> Check the Bluetooth specification. Every inquiry result contains a 3
> byte class of device value.
>
> Regards
>
> Marcel
>
>
Yes I'known but the class isn't sufficient to known if remote device has
an obex push service, sure can I remove all classes
that certainly did not have this service but it's a form of
optimization rather than a solution to the problem.
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-11-27 11:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-26 20:49 [Bluez-devel] (no subject) Fabrizio Guglielmino
2007-11-27 7:14 ` jm
2007-11-27 10:56 ` Fabrizio Guglielmino
2007-11-27 8:25 ` Marcel Holtmann
2007-11-27 10:51 ` [Bluez-devel] Scan and push images Fabrizio Guglielmino
2007-11-27 11:06 ` Marcel Holtmann
2007-11-27 11:13 ` Fabrizio Guglielmino [this message]
2007-11-27 11:47 ` Marcel Holtmann
2007-11-27 12:52 ` Fabrizio Guglielmino
2007-11-27 13:08 ` Manuel Naranjo
2007-11-27 13:25 ` 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=474BFBF5.50500@infitsrl.com \
--to=guglielmino@infitsrl.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;
as well as URLs for NNTP newsgroup(s).