-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Oops, misunderstanding all around, sorry about that...
Maybe I can try and explain.
Here's how I would define the various UA-sniffing techniques :
1 - Client-side :
- Parse : 'read' and interpret 'known' elements in appName,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/10/2014 09:38, Jonas Sicking wrote:
On Thu, Oct 2, 2014 at 9:24 PM, eberhard speer jr.
ses...@ducis.net wrote:
If you are interested in the intricacies of UA-sniffing, client
and server-side, the use-cases, the esoterica etc I'll gladly
gladly contribute
what I can.
Regards,
eberhard speer jr.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)
iQEcBAEBAgAGBQJULiUDAAoJEOxywXcFLKYc/BYH/RsrgBLLQHcgMfoEp2mU8bKW
u5Hrgb1mEIXNp3GO41JW4dX7J9rxTBYlrwMOnznLq2GwM7awiWBVPYvL4cgokAvY
xc3lesplBbNONCNq5xNPWHfDHTfxewjyOSPEnH9M
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I understand the focus is on the client-side, understandably, but
please note that on both client and server side UA sniffing is used
for 'responsive' design. On the server side for example it can be used
to route requests or format responses.
