I have a situation in my webapp where the user (administrator) can 'Publish'
items. I need to make it so only one person can 'publish' at a time. Would
this be a valid use of 'isThreadSafe'? Would it make user #2 wait until the
page had finished processing for user #1? It would save me from
On Mon, Dec 20, 2004 at 09:33:11AM -0500, Kurt Overberg wrote:
: I have a situation in my webapp where the user (administrator) can
: 'Publish' items. I need to make it so only one person can 'publish' at a
: time. Would this be a valid use of 'isThreadSafe'? Would it make user #2
: wait
I compared two servlets' source code compiled from JSPs,
at the beginning of one jsp I add page directive:
[EMAIL PROTECTED] isThreadSafe=false %
and the other, [EMAIL PROTECTED] isThreadSafe=true %.
But the two servlet are the same , I had thought the first
servlet will implement
Howdy,
I compared two servlets' source code compiled from JSPs,
at the beginning of one jsp I add page directive:
[EMAIL PROTECTED] isThreadSafe=false %
and the other, [EMAIL PROTECTED] isThreadSafe=true %.
But the two servlet are the same , I had thought the first
servlet will implement
Hi,
Don't rely on SingleThreadModel, it's more than deprecated: it's evil.
Don't use the isThreadSafe directive, don't use SingleThreadModel.
Yoav Shapira http://www.yoavshapira.com
-Original Message-
From: zerol tib [mailto:[EMAIL PROTECTED]
Sent: Monday, December 06, 2004 10:23 AM
I have to agree with Yoav. You shouldn't use the isThreadSafe
directive unless you absolutely have to (why would you?). I would
reconsider your design if you think you need to use this directive.
On the other hand, AFAIK, the servlet spec only requires the container
to guarantee synchronized
