All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Multithread Service Discovery
Date: Sun, 01 Apr 2007 14:58:08 +0200	[thread overview]
Message-ID: <1175432288.5815.285.camel@violet> (raw)
In-Reply-To: <BAY124-W5118C7F2144DA03833009AF0610@phx.gbl>

Hi Robert,

> Thanks again for your help, I'm glad that i now know simultaneous
> service requests is -not- an option, which means that my current
> solution isn't so bad. At the moment i run an HCI enquiry and then
> loop through the results, SDP each device for the obex channel and
> initiate a push to them. The speed is pretty good, we just have the
> problem that if we've got a slow 1.1 device in range, they can hold up
> the queue a couple of seconds.
>  
> Basically i'm looking to build a small application which distributes
> calendar information to people as they walk past my clients pub. But
> as people are walking past it is important that we discover the device
> and its services as quickly as possible, so they dont walk out of
> range before we get chance to push the file to them.
>  
> Have any of you had experience of working with this before? or have
> any advice on it?

sort the list of found devices by RSSI to contact the devices in range
first. Modify the page timeout and link supervision timeout to faster
detect page failures and disconnected links.

You can use two dongles. So one for running the inquiry and the other
one for service discovery and pushing the actual files.
 
> With regards to pushing a file to them, is ObexObjectPush my best
> option? or is ObexFTP replacing this now?

No. OBEX Push is for pushing files and OBEX FTP is for FTP like access
to a file storage.
 
> Using python wont be an issue, I find that most of these top level
> languages are very similar so learning the syntax for python wont be
> an issue, its just a case of finding some good examples to look it.

The inquiry and service discovery is kinda simple via D-Bus and Python.
For pushing the actual file, we don't have a real Python binding.

Regards

Marcel



-------------------------------------------------------------------------
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-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2007-04-01 12:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-01 10:25 [Bluez-users] Multithread Service Discovery Robert Rawlins
2007-04-01 12:58 ` Marcel Holtmann [this message]
2007-04-01 14:04 ` Malte Steiner
  -- strict thread matches above, loose matches on Subject: below --
2007-04-01 14:00 Robert Rawlins
2007-03-31 19:58 Robert Rawlins
2007-03-31 20:44 ` Loreno Oliveira
2007-04-01  7:01 ` Marcel Holtmann
2007-03-30 19:33 Robert Rawlins
2007-03-30 19:45 ` Malte Steiner
2007-03-31 13:44   ` Marcel Holtmann

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=1175432288.5815.285.camel@violet \
    --to=marcel@holtmann.org \
    --cc=bluez-users@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.