Dominic wrote:
> Kevin, thanks for your reply.
>
> Let me put my question in another way.
>
> Let's assume the following:
> - I don't want to set up SQL server to store session (say, for the
> sake of performance) and so I use "Inproc" mode for session state,
> - The load-balancer DOES support sticky-session, and
> - I don't want to use abacus
>
> Can I conclude that the session and viewstate information can be
> safely maintained in the web server in this web farm environment for
> mobile ASP.NET?
>
> Dom
>
>
>
> "Kevin Spencer" <kspencer@takempis.com> wrote in message news:<#2B4kiXzEHA.2876@TK2MSFTNGP12.phx.gbl>...
>
>>>I don't quite like the idea of storing session information in separate
>>>web server or database server. It is because one important reason of
>>>running a web-farm is to increase availability. If the web-server / DB
>>>server storing the session information fails, the whole web-farm will
>>>fail to run properly. Right?
>>
>>It is always good to be aware of, and account for, points of failure. As
>>this seems to be the only issue which troubles you, let me remind you that
>>SQL Servers can be mirrored, and that you can set up a Fail-Over SQL Server
>>in case the problem you described occurs.
>>
>>If, on the other hand, you're trying to make sure that there are absolutely
>>NO points of failure, I would suggest using an abacus. ;-)
>>
>>--
>>HTH,
>>Kevin Spencer
>>.Net Developer
>>Microsoft MVP
>>Neither a follower
>>nor a lender be.
>>
>>"Dominic" <domtam@hotmail.com> wrote in message
>>news:2b7c69f5.0411171708.dd94368@posting.google.com...
>>
>>>My question is about how to maintain view state in mobile ASP.NET
>>>across postback / request in a web farm environment.
>>>
>>>First of all, let's assume the web-farm does NOT use stick-session
>>>feature. In other words, different web servers may serve different
>>>requests in the SAME session.
>>>
>>>In non-mobile ASP.NET, my understanding is that the view state
>>>information is passed between each client browser and server with
>>>every post-back. Even if the request is handled by another different
>>>web server in the web farm, the viewstate information is still
>>>available in the postback because it is stored in the request (not the
>>>web server). Therefore, maintaining viewstate information is not an
>>>issue in a web farm environment.
>>>
>>>However, in mobile ASP.NET, view state is stored in session object
>>>(ref: Building Microsoft ASP.NET Applications for Mobile Devices by
>>>Andy Wigley and Peter Roxburgh - p. 386). In order to maintain view
>>>state, is it true that the ONLY option is to store the session
>>>information in a separate web server or database server (setting
>>><sessionState mode="StateServer" or "SqlServer"> in web.config)?
>>>Without doing that, how can we maintain the viewstate across postback
>>>in a non-sticky-session web-farm environment?
>>>
>>>I don't quite like the idea of storing session information in separate
>>>web server or database server. It is because one important reason of
>>>running a web-farm is to increase availability. If the web-server / DB
>>>server storing the session information fails, the whole web-farm will
>>>fail to run properly. Right?
>>>
>>>Any insight is much appreciated! Thanks!
>>>