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.
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.
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. Is this secure ?
Thanks...
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
