-----------------------------
Please read the FAQ!
<http://java.apache.org/faq/>
-----------------------------
> Hi;
>
> I am developing an application which needs to keep track of user
> information on the server. Each user will have about 2 Kb information
> on the server and I am expecting to have about 50-100
> concurrent users.
>
> I thought about keeping this information in the database, but
> I will be
> using mySQL for this project and regarding the fact that it doesn't
> have integrity constraint check, I am not sure how reliable it would
> be, besides I need to access to this data frequently which will slow
> down the user response.
Actually the lack of integrity constraint checks is a performance benefit. If you are
writing All the code that hits the database
then you only need to worry about how good you are ;-) A database that lacks integrity
constraints is really only a liability in an
environment where multiple programmers/applications need to access the db.
> So, for now, I am planning to use HTTPSession, I will keep the user
> information in a Hashtable and keep the hashtable in HTTPSession
> object, but I don't know how good it is. I mean is it efficient and
> reliable to keep that much of information in HTTPSession ? Can it be a
> serious bottleneck ? I would really appreciate comments about this.
>
I'm sure others will chime in but as far as dynamic data goes 200k should be a fairly
trivial amount. Hashtables are quite efficient
for information retrieval.
> Also, when I can't use a cookie and encode the URL for transferring
> User ID between requests, the URL becomes something like
> http://www.xxx.com/JSERVUID=some_junk_data. Do you think this
> is secure
As opposed to what?
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
