linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Scan and push images
Date: Tue, 27 Nov 2007 12:06:27 +0100	[thread overview]
Message-ID: <1196161587.17196.37.camel@aeonflux> (raw)
In-Reply-To: <474BF69A.3030008@infitsrl.com>

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.

> 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.

> - 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



-------------------------------------------------------------------------
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

  reply	other threads:[~2007-11-27 11:06 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 [this message]
2007-11-27 11:13       ` Fabrizio Guglielmino
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=1196161587.17196.37.camel@aeonflux \
    --to=marcel@holtmann.org \
    --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).