"Craig R. McClanahan" wrote:
> [...]
> Synchronization of application level data objects is an application level
> issue, not a server problem. Servlets and JSP pages operate in a multithreaded
> server environment. The principles about what and when to synchronize are easy
> to learn and apply, and should not be built in to the server that doesn't know
> which of your objects needs protection and which do not.
>
> Askling that the server to "protect you from yourself" by serializing requests
> to the same session is like buying a steak knife but covering up most of the
> blade with rubber -- you can still (slowly) cut the meat, but you're not so
> much at risk for cutting your finger. For myself, I'd rather learn to use the
> knife safely so I can take advantage of its abilities.
Yes, I agree 100%. Also, I don't see synchronization as something the typical
non-programmer using JSP need to be concerned with. I guess it comes back to the
tag vs scriptlet discussion again. Non-programmers using JSP to develop dynamic
pages need components developed by programmers to do their job: Beans, custom
tags, and other objects that may be shared within the application and session
scopes. And programmers must know how to deal with synchronization issues in
any multi-threaded environment.
--
Hans Bergsten [EMAIL PROTECTED]
Gefion Software http://www.gefionsoftware.com
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
