[thelist] ASP questions

on 5/11/00 1:16 PM, Scott Dexter at sgd@ti3.com wrote:

> They're smart, and have some ASP knowledge.
> 
> The ASP Session object uses server-side memory to persist client sessions.
> IIS passes a sessionid cookie to the browser, and uses that id to relocate
> the session information. There are a couple significant drawbacks to using
> the Session object: 1) you can't use it across servers, and 2) you can eat
> server resources, and if you're new to ASP, you can really hose yourself by
> setting a Session object to an object that isn't threaded properly, thereby
> throttling IIS to a single thread (You basically hose performance in a major
> way)
> 
> --The workaround to persisting session state is either client side cookies
> or persisting to a db or filesystem.

got it, thanks.
I was thinking session variable == cookie, but I was wrong.

Well I guess - session variable == cookie
but ... cookie != session variable

:)

James.