You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tapestry.apache.org by David Solis <ds...@legosoft.com.mx> on 2003/04/11 04:39:32 UTC

Browser sniffer

After a little research, I implemented the logic for a browser sniffer.
 
What is the best strategy to incorporate in Tapestry?
 
Its lifecycle could be:
 
1.	At beginning, BrowserSniffer (BS) collects information about
user agent and other http header variables. BS requires a IRequestCycle
as parameter.
2.	Its scope is per session like Visit. BS can provide a
serializable bean, i.e. BrowserInfo (BI). BI can be stored in the Visit
 
Main question is what should be BS? 
Alternatives are a non visual component, a simple bean or a engine's
object like Visit or Global.
 
Any ideas?
 
David