All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Harald S. Hanssen" <haraldsh@stud.cs.uit.no>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] OBEX still not supported in Bluez?
Date: Sun, 26 Aug 2007 11:51:08 +0300	[thread overview]
Message-ID: <46D13EFC.502@stud.cs.uit.no> (raw)

Eventhough I can find the OBEX mentioned in the API, it does seem like 
Bluez does not support the protocol.

I found a webpage (http://wireless.klings.org/main.php/How-To/OBEX/) 
mentioning that Bluez does not support OBEX quite yet. Instead I have to 
use OpenObex. However OpenObex does not have a python binding, so I 
hoped to avoid it as much as I could.

Any ideas?
Btw, is this the right list for getting clues about how to program with 
Bluez?

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

                 reply	other threads:[~2007-08-26  8:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=46D13EFC.502@stud.cs.uit.no \
    --to=haraldsh@stud.cs.uit.no \
    --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.