 | Mailing List | | Home | | Forum Home | | JBoss - Java Application Server | | Tomcat - JSP/Servlet container | | Struts - A MVC web framework | | iText - An open source PDF Java Library | | JDOM - JDOM XML Parser | | J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition | | JSP - A mailing list about Java Server Pages specification and reference | | J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog | | Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology | |
Struts & Hibernate
|
|
|
| | | -none- | -none- 2007-09-04 - By samk@(protected)
Back
See Thread at: http://www.techienuggets.com/Detail?tx=11977 Posted on behalf of
a User
Nothing to do with Tomcat. Look up the Singleton pattern and it will teach you
what you need.
In Response To:
I have a unique situation where I'm building a polling server for a
Flash/Flex application. I want to turn information around very quickly
between clients and therefore don't want to use a database if I don't have
to. What I want to do is store information in a few static variables used
in a servlet. I'm looking for speed more than anything as the clients will
be polling the server every 2-3 seconds. I'm expecting about 100 to 500
(max) clients at any given time. What I'm curious about is how Tomcat
handles static variables. Coming from ASP.NET experience I know that using
static variables with IIS they are held in the app domain and the app domain
can be reloaded by IIS for a number of reasons (config files changed, files
changed, etc.) This kinda makes using static variables in ASP.NET and IIS a
bit tricky and unreliable. So the question I have is how does Tomcat handle
static variables then? When would they get reloaded/recycled, etc.? I'm
aware I could use something like memcached to mimic what I'm doing but again
I'd rather stick to static variables if possible for the sake of simplicity.
Thanks for any help on this.
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To start a new topic, e-mail: users@(protected)
To unsubscribe, e-mail: users-unsubscribe@(protected)
For additional commands, e-mail: users-help@(protected)
|
|
|
