Sharing session via InProc

Hello all,
I’m looking for some general information about sharing the session but
haven’t found any resources that confirm my conceptions. All the discusis
ons
about sharing the session revolve around services and SQL
It appears possible to run multiple servers off one servers InProc provided
the stateConnectionString is configured properly, true?
Also it appears if InProc is used, data does not need to be serialiazble,
true?
Is there anyway programmatically to prevent users from deploying a web
garden via InProc?
Thanks,
Billsee >>
"Bill Belliveau" <BillBelliveau@.discussions.microsoft.com> wrote in message
news:6EE589C5-3ED6-4BDE-BCEA-FE508E94EDD7@.microsoft.com...
> Hello all,
> I'm looking for some general information about sharing the session but
> haven't found any resources that confirm my conceptions. All the
discusisons
> about sharing the session revolve around services and SQL
> It appears possible to run multiple servers off one servers InProc
provided
> the stateConnectionString is configured properly, true?
>

manager. inproc means the session objects are stored in global variables in
the current app domain. if you don't want to use sqlserver, there is a
server based session manager (stores session data in memory), but it
requires serialization.
> Also it appears if InProc is used, data does not need to be serialiazble,
> true?
>

> Is there anyway programmatically to prevent users from deploying a web
> garden via InProc?
>

> Thanks,
> Bill
Bill,
You might have been better off if someone else answered - hopefully someone
will correct me if i'm wrong.
[1] - InProc sessions cannot be shared across multiple servers. The
stateConnectionString referes to the ASP.Net session state server,
identified by the StateServer mode
[2] - That's right (the data is stored in memory and not serialized as a
string)
[3] - You can access Session.Mode to see which mode the session state is
using, and throw an exception if it's InProc. The question is where to do
that..Ideally it would in the Application_Start, except the session isn't
available then. That only leaves the PreRequestHandlerExecute event:
Private Sub Global_PreRequestHandlerExecute(ByVal sender As Object, ByVal
e As System.EventArgs) Handles MyBase.PreRequestHandlerExecute
If Session.Mode = SessionStateMode.InProc Then
Throw New ApplicationException("Can't be in proc")
End If
End Sub
Karl
"Bill Belliveau" <BillBelliveau@.discussions.microsoft.com> wrote in message
news:6EE589C5-3ED6-4BDE-BCEA-FE508E94EDD7@.microsoft.com...
> Hello all,
> I'm looking for some general information about sharing the session but
> haven't found any resources that confirm my conceptions. All the
discusisons
> about sharing the session revolve around services and SQL
> It appears possible to run multiple servers off one servers InProc
provided
> the stateConnectionString is configured properly, true?
> Also it appears if InProc is used, data does not need to be serialiazble,
> true?
> Is there anyway programmatically to prevent users from deploying a web
> garden via InProc?
> Thanks,
> Bill
Karl,
Thanks for clearing that up. I did find the Session.Mode, but I wasn't sure
if Inproc process, provided permissions, could be accessed from another
server. The fact that Inproc is always local is never stated and some
content I found hinted that it could be used.
So to reiterate:
Single server
Inproc – local process (ASPNET / Application Pool) that cannot be accessed
remotely. stateConnectionString is ignored.
Web garden
StateServer service or SQL Server (requires serialization)
Thanks again,
Bill
"Karl" wrote:

> Bill,
> You might have been better off if someone else answered - hopefully someon
e
> will correct me if i'm wrong.
> [1] - InProc sessions cannot be shared across multiple servers. The
> stateConnectionString referes to the ASP.Net session state server,
> identified by the StateServer mode
> [2] - That's right (the data is stored in memory and not serialized as a
> string)
> [3] - You can access Session.Mode to see which mode the session state is
> using, and throw an exception if it's InProc. The question is where to do
> that..Ideally it would in the Application_Start, except the session isn't
> available then. That only leaves the PreRequestHandlerExecute event:
> Private Sub Global_PreRequestHandlerExecute(ByVal sender As Object, ByV
al
> e As System.EventArgs) Handles MyBase.PreRequestHandlerExecute
> If Session.Mode = SessionStateMode.InProc Then
> Throw New ApplicationException("Can't be in proc")
> End If
> End Sub
>
> Karl