Re: RV: Session & Context variables architecture problem

2010-11-01 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Pid, On 10/28/2010 5:36 PM, Pid wrote: > I would suggest that you created a class which periodically updated all > the values by selecting the data in the DB and storing the result in the > Context. > > Implementing a ServletContextListener will give

Re: RV: Session & Context variables architecture problem

2010-10-29 Thread Pid *
y S.A > ni su autor se hacen responsables por las alteraciones que pueda sufrir este > mensaje a partir de su envio. > > -Mensaje original- > De: Pid [mailto:p...@pidster.com] > Enviado el: jueves, 28 de octubre de 2010 19:36 > Para: Tomcat Users List > Asunto: Re:

RE: RV: Session & Context variables architecture problem

2010-10-29 Thread falvarez
OM Uruguay S.A ni su autor se hacen responsables por las alteraciones que pueda sufrir este mensaje a partir de su envio. -Mensaje original- De: Pid [mailto:p...@pidster.com] Enviado el: jueves, 28 de octubre de 2010 19:36 Para: Tomcat Users List Asunto: Re: RV: Session & Contex

Re: RV: Session & Context variables architecture problem

2010-10-29 Thread Ronald Klop
Just query the database. Enable query caching in mysql. And only optimize in java if you see a bottleneck. My mysql does 15000 queries/sec. What is your expectation of number of queries? Ronald. Op donderdag, 28 oktober 2010 19:31 schreef falva...@geocom.com.uy: Dear All,

Re: RV: Session & Context variables architecture problem

2010-10-28 Thread Pid
On 28/10/2010 18:31, falva...@geocom.com.uy wrote: > Dear All, > I'm currently using Tomcat 6.0.28 and having some doubt on > how to solve and implement this problem: >My webapp has a MySQL Database with a table > named "parameters", in which we have

RV: Session & Context variables architecture problem

2010-10-28 Thread falvarez
Dear All, I'm currently using Tomcat 6.0.28 and having some doubt on how to solve and implement this problem: My webapp has a MySQL Database with a table named "parameters", in which we have just two columns ("property" and "value"). This table is