W3C home > Mailing lists > Public > public-ddwg@w3.org > July 2005

RE: Mobile phone capabilities list?

From: Luca Passani <luca.passani@openwave.com>
Date: Wed, 27 Jul 2005 10:07:12 +0200
To: <public-ddwg@w3.org>, <www-mobile@w3.org>
Message-ID: <BFS-FE-PRD120lbhsKd00000215@bfs-fe-prd1.myopwv.com>

>As has been said ... the IMEI can be used to know about the radio device
>being used. But that does not assure knowledge of the client capabilities
>e.g. laptop / PDA with GPRS card. 
>There is much more than is needed to be known.

Really? where does this requirement come from?

I have talked with hundreds of developers from very varied backgrounds
over the past few years, yet I can't recall a scenario where wireless
developers were going mad trying to identify if it was a laptop over a GPRS
connections they were trying to send an MMS too.
On the other hand, WURFL only covers WAP, markups, WAP Push, MMS, J2ME,
EMS, ringtones, usability, wallpapers and streaming. You may be aware of
other reasonably common scenarios outside of the domain of those
In that case, I would really be curious to hear about them.
Also, I think there is a misunderstanding here. Some may find it useful to
use IMEI as a key to figure out device capabilities. This would be an extra
feature. Nobody ever said that this should be the only way. In most cases,
HTTP headers are much better for that purpose. IMEI is useful under a few
- you have access to the IMEI code for the device of the subscriber you want
to serve.
- you don't have an HTTP request coming from the device


Received on Wednesday, 27 July 2005 08:07:46 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:00:12 UTC