From: Pedro Monjo Florit <pedro.monjo@futurlink.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Detect the type of remote device
Date: Wed, 23 Feb 2005 18:42:00 +0100 [thread overview]
Message-ID: <421CC068.3050202@futurlink.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 742 bytes --]
Hi everybody:
While using the BlueZ API's we have discovered that it's difficult to
find which kind of device (brand and model) we are talking to. We are
writing an application that delivers an image to any device passing by,
taking into account its screen width, height and color depth, but
without any prior knowledge of the device.
Using WAP we have access to the HTTP headers from where you can parse
the User Agent Profile (UAProf), but we have not found any similar
function in Bluetooth. In fact, there is the PnPInformation Profile, but
nowadays is supported in very few devices.
Is there any function or mechanism to retrieve the UAProf data (or
anything similar) using the BlueZ library?
Thanks & regards,
Pedro Monjo
[-- Attachment #2: Type: text/html, Size: 1108 bytes --]
next reply other threads:[~2005-02-23 17:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-23 17:42 Pedro Monjo Florit [this message]
2005-02-24 10:52 ` [Bluez-users] Detect the type of remote device 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=421CC068.3050202@futurlink.com \
--to=pedro.monjo@futurlink.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