You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@devicemap.apache.org by "eberhard speer jr." <se...@ducis.net> on 2014/01/17 11:54:44 UTC

ACUS - topic

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi again,

here's a quick sketch of a relevant topic :

I identify 3 different methods of device detection :

- - Resolve/Map : 'real' DDR : 'known' elements in an user-agent string
allow it to be mapped to a 'record' in a device database which returns
properties of the device. [returns info not contained in ua-string]

- - Parse : 'read' and interpret 'known' elements in an user-agent
string and return results. [returns only info contained in ua-string]

- - Probe : run javascript on the connected client and have it return
the properties found. [returns supported navigator properties]

For one and the same user-agent string the 3 methods are likely to
return 'contradicting' results.
Explaining why this is shows that these 'contradictions' add valuable
information about the device/user-agent [and its user] in certain
use-cases [traffic analysis] while in other cases choosing the wrong
method leads to 'errors' [content formatting].

Understanding the differences between the methods and their results is
rather vital for getting the device-detection thing right.

esjr
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJS2Qv0AAoJEOxywXcFLKYcr7IH/1YmQxrvoprGkulWqpfBCwJB
uvE2SJpCgPLE3gJ4FhVKfZEg4IJLTdvFX6Plx72Iu4mGxnhicgsqI0DRtxKUVWzK
2OVkmPR7NiYTpw9nDaP1kneNK6wYfZv65FQ/ddcbD00TqxA6WmQ7TIIsr4GwU8Eb
gpAzdmGCoqbcMrONa6bXSdDn1YUNA1aJyWc9o+DUR8c9WPOiNModp2I5+LkG17NO
0SceIi3iNj6xVYgwIIFswTAKwqjCGjcLdngawOSQl3LFvhBChy17XIj9ZDQrdYeZ
nk+TA6hQxv4ynb1HobinmQTnJ4URHSleQKmH2Lk2ZF+EoGnsIU0WVLwfqKLI9TI=
=T29R
-----END PGP SIGNATURE-----