Re: Worker process and Session state
- From: "bruce barker \(sqlwork.com\)" <b_r_u_c_e_removeunderscores@xxxxxxxxxxx>
- Date: Mon, 23 Oct 2006 12:44:05 -0700
all asp.net code run in an appdomain hosted by the worker process. a process
can host multiple domain. inproc sessions are stored in the appdomain, so
should not be used with web gardens or web farms.
sessionid are just id tickets stored in cookie. one is generated if the
cookie does not currently have one. then session is looked up (or created)
by the id.
so a session id will be shared across a web garden or farm, but if inprc
session is used, the session data will not be shared.
-- bruce (sqlwork.com)
"Diffident" <Diffident@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4DA25172-BEBF-4266-802E-687FDA2B6764@xxxxxxxxxxxxxxxx
Hello All,
I have a question about worker processes and session state. If I set-up a
web farm architecture by having multiple worker processes serving a single
application, how will the session state be affected?
For example, let's consider that a user A requested for page A and after
some time the same user requests page B. In both these cases, will a new
Session ID be created?
If we create a web farm architecture, will each worker process be in it's
own application domain?
Can someone please explain me what's the relation between worker process
and
application domain? App. domain hosts worker process or is application
domain
inside worker process?
Thanks for your clarifications!!
.
- Prev by Date: Global.aspx in VS 2005
- Next by Date: Re: TRACE doesn't work on the remote box
- Previous by thread: Global.aspx in VS 2005
- Next by thread: Re: Large (over 1 meg) website takes long time to post back W/O Viewst
- Index(es):
Relevant Pages
|