Re: UA strings

On Mon, Jun 21, 2004 at 03:36:55 +0000, ganesh@t-email.co.uk wrote:
> > For example: Nokia3100/1.1 (06.01) Profile/MIDP-1.0 Configuration/CLDC-1.0
> Yes. Where I work  we see multiple versions of a browser throughout a product's 
> lifecycle. Usually these are just bugfixes (or bug includes), but sometimes 
> major changes in functionality can occur, such as the addition of XHTML 
> to some Nokias mid-lifecycle. Browsers vary between countries and operators 
> too.

Oh dear ! One more thing. Can Nokia upgrade it's browser when the device
is "out in the wild"? Does it have some sort remote update system? Or
can I assume once a device ships with version 1.1 it will always be 1.1.

> Doesn't appear so. Nokia gets around the problem by issuing a fresh UAProf for 
> each device with an Rnnn at the end of the UAProf name referring to each 
> version. This doesn't seem to map exactly, however. Your device advertises 
> itself in its headers as version 1.1 of the 3100, but there's only an R100 
> UAProf.

Doesn't this strike you as a tiny bit silly to have to have an entirely
new UAProf for a UA agent revision? Is this how UAProf was designed, or
this is how Nokia has implemented it?

> > [1] http://natalian.org/archives/2004/06/18/nokia-inline-image-test/
> You seem confused by what "file too large" means on a Nokia. It refers to 
> the byte-size of the file (eg, it's bust the deck limit or the device has 
> simply run out of memory): the geometrical size of the image doesn't cause 
> this error.

Oh really? I must try that, when my stupid operator's GPRS service
starts to work again...

Received on Monday, 21 June 2004 11:59:35 UTC