http://www.ronaldwidha.net/2009/03/23/why-you-should-never-use-in-proc-session/ podcast addict, believes in occam razor, software consultant Thu, 02 Feb 2012 23:00:33 +0000 hourly 1 http://wordpress.org/?v=3.0.5 http://www.ronaldwidha.net/2009/03/23/why-you-should-never-use-in-proc-session/comment-page-1/#comment-568 ronaldwidha Fri, 25 Feb 2011 06:55:44 +0000 /Stuff/Why-you-should-NEVER-use-in-proc-session.aspx#comment-568 Bigger web apps always use staggered deployment. The new version will get rolled in in stages, little by little traffic is redirected to the new versions. This is usually done by detaching a 'slice' of servers (front end, db, cache, session server) from the load balancer. New incoming traffic will be redirected to only the servers with the new version of software. Bigger web apps always use staggered deployment. The new version will get rolled in in stages, little by little traffic is redirected to the new versions. This is usually done by detaching a 'slice' of servers (front end, db, cache, session server) from the load balancer. New incoming traffic will be redirected to only the servers with the new version of software.

]]> http://www.ronaldwidha.net/2009/03/23/why-you-should-never-use-in-proc-session/comment-page-1/#comment-567 Nospam Fri, 25 Feb 2011 05:01:47 +0000 /Stuff/Why-you-should-NEVER-use-in-proc-session.aspx#comment-567 Out of proc session doesn't explicitly enable you to deploy new code while sessions are alive. What if your session changes? What if different object types are used? The session won't deserialize correctly and you'll be SOL. Out of proc session doesn't explicitly enable you to deploy new code while sessions are alive. What if your session changes? What if different object types are used? The session won't deserialize correctly and you'll be SOL.

]]>