From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Detect the type of remote device
Date: Thu, 24 Feb 2005 11:52:12 +0100 [thread overview]
Message-ID: <1109242332.5645.14.camel@notepaq> (raw)
In-Reply-To: <421CC068.3050202@futurlink.com>
Hi Pedro,
> 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?
actually the PnP stuff is available in Bluetooth and it is called Device
ID, but there are not a lot of devices that supports this.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2005-02-24 10:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-23 17:42 [Bluez-users] Detect the type of remote device Pedro Monjo Florit
2005-02-24 10:52 ` Marcel Holtmann [this message]
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=1109242332.5645.14.camel@notepaq \
--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.