-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Reza,
I know to you #2 and #3 are the same, because they 'work' the same way technically in DeviceMapClient and I agree with that. The difference is in the fact that the DDR supplies external information while parsing extracts the 'internal' information in the UserAgent string. In #2 you 'look-up' a device's browser, while in #3 you 'extract' the browser from the ua-string. [I known, behind the scenes, technically in both cases it's a pattern being 'matched' and in both cases a 'look-up' of a value corresponding to that match.] That is why the browser returned using #2 may be different from the one using #3. Method 3 will require more patterns : possibly up to one for each possible 'data-point' in a UserAgent string, while method 2 'only' requires the patterns to identify the unique device and then look up it's properties, irrespective of what the rest of the ua-string says. So, they work the same way, but what they do is quite different. I agree that for us that is pretty academic, but for Users it is an important distinction they need to be aware of. esjr -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJT2892AAoJEOxywXcFLKYc7D8H/AivcVa68p1l6W2S9KORtqAI UyC3yVkvFAyHjwBMUhOWIia2LzjwhsRCyfNj/o4HkQ+mpJCtD+7MHv+aNR/R6mfn y0GVwkZE2DP35nnFDWqXG7/Y5QCZJzfMft2YLRrqT/5DZGM1yb1BUYeaUhlgrnov /aqvGfPP5HTfqvMqLPLlzG0hG5WLMrL+pFm8PN44ZD76xo9XAQBBAGR/2Fiqa9il KzI9JYqI4d2LPUjwCw6O8DNJupLEbah/RVljkp3BJ7IfpSpj5TvGyCoEncvrE/An ZmwGZZIytauE4Epe+UZvYP2gGqmjMOkvc4EvI5ba2v1STQfScK71tkyRIYFhstY= =ilYH -----END PGP SIGNATURE-----
