tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Solis" <dso...@legosoft.com.mx>
Subject Browser sniffer
Date Fri, 11 Apr 2003 02:39:32 GMT
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?

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message