Re: Faking Entity Beans in Tomcat?
From: Murray (parps_at_SPAMOFFoptusnet.SPAMMAGE.com.au)
Date: 07/16/04
- Next message: dave: "OO design in servlet design question"
- Previous message: Michael Borgwardt: "Re: what is a stack"
- In reply to: Andoni: "Faking Entity Beans in Tomcat?"
- Next in thread: Andoni: "Re: Faking Entity Beans in Tomcat?"
- Reply: Andoni: "Re: Faking Entity Beans in Tomcat?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 16 Jul 2004 21:49:42 +1000
> 1. It has to be possible to update any user in real time or to create a
new
> one and have them function immediately.
If it wasn't for this requirement, you could simply stick the user data into
the session. I assume you mean you want to be able to modify the user's
state from some other "place" in the application, i.e. outside the user's
session by an admin user or something along those lines. Is that what you
mean?
> 2. I don't know if there would be too much information being stored at
> application level?
Well obviously that depends on the amount of data involved, how many users
will be using the site concurrently, and the amount of memory available on
the server. All things that only you know at the moment ;-) But if the
queries to grab the data take a while, then I'd say it's an acceptable
compromise to store the data in memory to improve performance, as long as
it's not a massive amount of data.
- Next message: dave: "OO design in servlet design question"
- Previous message: Michael Borgwardt: "Re: what is a stack"
- In reply to: Andoni: "Faking Entity Beans in Tomcat?"
- Next in thread: Andoni: "Re: Faking Entity Beans in Tomcat?"
- Reply: Andoni: "Re: Faking Entity Beans in Tomcat?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|