Milt Epstein wrote:
> ...
> I doubt very much that this is the case. For one thing, there's no
> reason a cleanly designed, thread safe solution that doesn't use
> SingleThreadModel should not be portable across servlet containers. I
> don't see any portability benefits to SingleThreadModel. And again,
> it's misleading, because using it does not really guarantee thread
> safety. This has been discussed on this list many times before,
> anyone interested can check the archives.
>
> BTW, all those brackets and smiley faces just make your posts harder
> to read.
>
Hi Milt, thanks for your email :-) but I have some questions:
0
perhaps other people have already known a perfect
way for Servlet_thread-security, but I don't know now,
and from several emails in Servlet-List, I find some
problem -- for example:
multi ClassLoders
multi Instances of the same Servlet class
...
so do you know a perfect solution for Servlet_thread-security ?
Can you post it to Servlet-List? I will try to test it :-)
1
so I guess perhaps only the [Servlet specification maker -- SUN-Servlet
group ] and the [Servlet engine provider] can give Servlet developers a
perfect solution.
2 -- so where is the [bridge]?
a and what is the [bridge] between [Servlet specification maker]
and [Servlet engine provider]? -- I guess the interface--
SingleThreadModel
perhaps is a good way.
b and what is the [bridge] between [Servlet engine provider]
and [Servlet developer]? -- I still guess that the interface--
SingleThreadModel perhaps is a good way.
BTW, the reason that I have to use [... ] is because my English
is not good:-)
please correct me ! Thanks in advance!
Bo
Nov.03, 2000
___________________________________________________________________________
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