Thanks for all who replied with good answers. I am working on fixing this problem.
Now I am curious about the technical design of the servlet. I wrongfully assumed
that a new servlet is loaded per connection, now I understood it is not the case.
Because the servlet is re-used, that's why whatever I declare as part of the class of the
servlet is shared by different connections. Since the servlet is loaded once and shared
among all connections, what are the exact parts that explicitly tells the servlet to keep
the data unique to the connection - I assume this would be the session right? Is it better
to put the non-shared data into __init__ (which is still part of the servlet class) or awake() ?


Lincoln



-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-discuss

Reply via email to