> On 9/10/06, Frans Bouma <[EMAIL PROTECTED]> wrote:
> > An old trick was that you have a common start page, and from
> > there, redirect with javascript to a different page. There,
> you set a
> > flag and redirect back to the main page, which now doesn't
> contain the javascript redirect code because of the flag (in
> the session).
>
> Session? Um, Server-side (Session) variables are pretty
> expensive in ASP.
depends. If you want to run a large website on a 512MB machine, then
yes, it's expensive.
> The higher you want to scale ASP, the less you use Session()
> variables.
You've to be careful no matter what, of course. But I really fail to
see why a boolean flag would cause a server melt-down.
If anything else fails, you could use a cookie. However, session objects are
pretty common nowadays, and the more you want to scale
a website, the more you also have to fall back onto caching, which also eat
memory. The fun thing is that memory is dead cheap.
But it's your call of course. :) You asked, I gave you a hint.
FB
===================================
This list is hosted by DevelopMentor® http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com
