It is possible, but IMHO its not a good idea.
Someone did this modifying the SQL Server script that builds the
ASPSessionState database (so this only works with SQL Server session state),
and I dont know how it works, but this is the only thing I found on it:
http://www.codeproject.com/useritems...sion_state.asp
"Gopal Prabhakaran" <prabhakar@takescm.com> wrote in message
news:O3Ng2RC4DHA.632@TK2MSFTNGP12.phx.gbl...[color=blue]
> Dear All
>
> Can we maintain session accross the webapplication, if so pls help me to[/color]
do?[color=blue]
>
> (i.e) = I have 2 webapplication namely
http://localhost/webapp1 ,
>
http://localhost/webapp2
>
> Can I use the session created in
http://localhost/webapp1 in
>
http://localhost/webapp2
>
> Pls Help me...
>
>
> Millions of thanx in advance
>
> --
> Thanx
> Gopal Prabhakaran
>
> "Elliot M. Rodriguez" <someemail> wrote in message
> news:O$sv$JC4DHA.1644@TK2MSFTNGP10.phx.gbl...[color=green]
> > Web garden scenarios, IMHO, are quite uncommon. I havent found anything[/color]
> yet[color=green]
> > that a solid server with enough RAM cannot handle.
> >
> > To me, the only thing to really watch is how you configure webgardens,[/color][/color]
and[color=blue][color=green]
> > manage session state. In IIS5 you need to modify the machine.config[/color][/color]
files[color=blue]
> so[color=green]
> > your application can support webgardens (the webgarden and cpumask
> > attributes). In IIS6 you can modify these settings on a per-application[/color]
> pool[color=green]
> > basis using the MMC.
> >
> > When you implement web gardens, each of the asp.net processes has its
> > processor affinity assigned to a specific processor. This can result in
> > sessions values apperaing lost, or empty. Using the session state[/color][/color]
service[color=blue]
> or[color=green]
> > SQL Server to manage your sessions is better in this case, as both serve[/color]
> as[color=green]
> > a single session repository.
> >
> > In web farming, application objects *are* supported. They haveto be
> > implemented, though, using either state service or SQL Server for the
> > reasons mentioned above (single session storage).
> >
> > You can implement caching for web farms, gardens, etc. under any[/color][/color]
scenario[color=blue][color=green]
> > using page output caching (varybyparam attribute). This should handle[/color][/color]
your[color=blue][color=green]
> > page cache question. I have implemented caching, both data and page, on[/color][/color]
a[color=blue]
> 5[color=green]
> > server web farm without any problems.
> >
> > With a web farm, you will have to change each machine's machineKey[/color]
> attribute[color=green]
> > under machine.config. These must match so each application's viewstate
> > requests match (otherwise you'll get corrupt ViewState errors). MS has a[/color]
> KB[color=green]
> > that applies to the above scenario (and source for an executable that[/color][/color]
will[color=blue][color=green]
> > build new hash keys) at
> >[/color]
>[/color]
http://support.microsoft.com/default...&Product=NETFr[color=blue]
> ame.[color=green]
> >
> > MSDN has a lot more detail for your other questions than I could ever
> > provide to you. but I hope this helps to start.
> >
> >
> >
> >
> >
> >
> >
> > "Steve" <Steve@discussions.microsoft.com> wrote in message
> > news:1a7a01c3e00c$af9bab70$a401280a@phx.gbl...[color=darkred]
> > > Hi
> > > What is difference between web farm and web garden?
> > >
> > > What i understand so far
> > > Web Farm
> > > Multi Server Environment
> > > Support Session share
> > > Application object not supported
> > > Caching not recommended (??)
> > > What about Page Cache (??)
> > >
> > > Web Garden
> > > Multi-Processor Scenario
> > >
> > > Rest same as Web Farm
> > >
> > > Expert Comments Expected
> > > Regards
> > > Steve
> > >[/color]
> >
> >[/color]
>
>[/color]
