Hi Bryan,
Have you got any further idea on this or does the things in my last reply
helps you a little? if there're anything else we can help, please feel free
to post here. Thanks,
Steven Cheng
Microsoft Online Support
Get Secure!
www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
--------------------
| X-Tomcat-ID: 127801003
| References: <
[email protected]>
| MIME-Version: 1.0
| Content-Type: text/plain
| Content-Transfer-Encoding: 7bit
| From: (e-mail address removed) (Steven Cheng[MSFT])
| Organization: Microsoft
| Date: Mon, 21 Nov 2005 08:09:29 GMT
| Subject: RE: IHttpHandler.IsReusable
| X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet
| Message-ID: <
[email protected]>
| Newsgroups: microsoft.public.dotnet.framework.aspnet
| Lines: 52
| Path: TK2MSFTNGXA02.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl
microsoft.public.dotnet.framework.aspnet:359737
| NNTP-Posting-Host: tomcatimport2.phx.gbl 10.201.218.182
|
| Hi Bryan,
|
| Welcome to ASPNET newsgroup.
| Regarding on the question about the IHttpHandler.IsReusable property, it
is
| used to indicate whether we can use a single HttpHandler instance to
| process multiple concurrent requests. Actually, we can consider each
| client requests as a worker thread on the serverside when being processed
| through the ASP.NET pipeline.. So if we want to mark our HttpHandler as
| IsReusable= ture, we need to make sure that the code in our HttpHandler's
| ProcessRequest method is threadsafe. In otherwords, the code in the
| ProcessRequest should not rely on any states or data which could be
| modified by other concurrent request threads (e.g. the Httphandler
class's
| non-static member fields....)...
|
| Thanks,
|
| Steven Cheng
| Microsoft Online Support
|
| Get Secure!
www.microsoft.com/security
| (This posting is provided "AS IS", with no warranties, and confers no
| rights.)
|
|
|
| --------------------
| | From: (e-mail address removed)
| | Subject: IHttpHandler.IsReusable
| | Date: Sun, 20 Nov 2005 20:53:20 -0600
| | Message-ID: <
[email protected]>
| | X-Newsreader: Forte Agent 3.1/32.783
| | MIME-Version: 1.0
| | Content-Type: text/plain; charset=us-ascii
| | Content-Transfer-Encoding: 7bit
| | Newsgroups: microsoft.public.dotnet.framework.aspnet
| | NNTP-Posting-Host: adsl-68-253-213-6.dsl.emhril.ameritech.net
68.253.213.6
| | Lines: 1
| | Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP14.phx.gbl
| | Xref: TK2MSFTNGXA02.phx.gbl
| microsoft.public.dotnet.framework.aspnet:359696
| | X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet
| |
| | I can't find much info on what makes an instance of the handler
| | reusable. If it maintains no internal state, I would assume that it is
| | safe to be reusable - correct? I have one that grabs a value from the
| | Session cache, twiddles some bits, and then writes the value back.
| | Since everything is a local variable (except the one from the cache)
| | am I safe in marking it as reusable?
| |
| | Thanks,
| | Bryan
| |
|
|
