Re: Loading properties from a file and keeping them in session

[Micael]

So, you probably would want to do that at application scope, rather than 
session scope?  If you are just storing the properties information, why 
transfer it to an object?  Just put the properties object at application 
level.  But, as James asked, why would you do this?  Why not use a 
database?  If you want speed, just hook in a little standalone hsqldb app, 
which has a really small footprint and would give you all the info you 
needed to put into application (or session) scope?



At 10:56 AM 3/27/03 -0500, you wrote:
On Thu, 2003-03-27 at 10:37, Pingili, Madhupal wrote:
> I am thinking of a mechanism to load properties (name=value pairs) from a
> properties file
> and store them in an object and finally store that object in session for
> using it later in the web application.
> Can anyone share their experience doing this kind of tasks?
I haven't tried that yet, but it sounds like that would be a pretty cool
(and quick) way to run my server out of memory.  Of course that depends
on number of users and a few other factors, but heck, if that's what we
want.
<me:mode serious="true"/>

I wouldn't do that if I were you.  Why would you need a different set of
bundle values for each user?  Besides the obvious memory overhead, what
is it that you are trying to accomplish?
>
> Thanks
> Reddy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
--
James Mitchell
Software Developer/Struts Evangelist
http://www.open-tools.org


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


LEGAL NOTICE

This electronic mail  transmission and any accompanying documents contain 
information belonging to the sender which may be confidential and legally 
privileged.  This information is intended only for the use of the 
individual or entity to whom this electronic mail transmission was sent as 
indicated above. If you are not the intended recipient, any disclosure, 
copying, distribution, or action taken in reliance on the contents of the 
information contained in this transmission is strictly prohibited.  If you 
have received this transmission in error, please delete the message.  Thank 
you  



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]