Linux bluetooth development
 help / color / mirror / Atom feed
From: Robert Rawlins <robert_rawlins@hotmail.com>
To: <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Multithread Service Discovery
Date: Sun, 1 Apr 2007 14:00:32 +0000	[thread overview]
Message-ID: <BAY124-W26C20CF401F912A4DCDABDF0610@phx.gbl> (raw)


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

Thanks for the advice Marcel, It'll prove invaluable i'm sure.
 
2 Dongles makes good sense, so i'll defiantly work with that arrangement to get things working fluidly. Is a single dongle able to handle a device enquiry and an SDP at the same time? or is that asking too much? I'm just trying to find the limitations of the hardware, just so i know what to expect as top performance.
 
>> Modify the page timeout and link supervision timeout to faster>> detect page failures and disconnected links.
 
I've seen you speak about this before and sounds like its a good way of managing the resources and speeding up the process. Could you explain a little more about modifying those page and link supervision time outs? is this something i do with my code or an alteration i need to make to the bluez stack? and are there any negative effects to making a change like this?
 
>> No. OBEX Push is for pushing files and OBEX FTP is for FTP like access>> to a file storage.
 
This is as i expected it would be, that's absolutely fine, i will continue to use our own USSP-Push like tool for doing the obex push, unless you have any other recommendations on doing this.
>> 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.
 
I'll agree that the Python and D-Bus certainly appears simpler on the face of things, from the samples i've seen, many written by yourself, the code certainly seems less complex that the alternative C methods. Do i need to look into PyBluez to use the python d-bus method, or is the PyBluez wrapper something else all together?
 
I've noticed while reading through the API documentation is lists a function for 'periodic' enquiry, is this something i should be looking to use in my application? my guess is that its a 'yes' and this function just repeatedly looks for devices in range?
Thanks again for all your help Marcel, and thanks to you other guys for your suggestions.
 
Rob
_________________________________________________________________
Try Live.com: where your online world comes together - with news, sports, weather, and much more.
http://www.live.com/getstarted

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

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

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

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

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

             reply	other threads:[~2007-04-01 14:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-01 14:00 Robert Rawlins [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-04-01 10:25 [Bluez-users] Multithread Service Discovery Robert Rawlins
2007-04-01 12:58 ` Marcel Holtmann
2007-04-01 14:04 ` Malte Steiner
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=BAY124-W26C20CF401F912A4DCDABDF0610@phx.gbl \
    --to=robert_rawlins@hotmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox