-----Original Message-----
Har, har, har! A *professional* who apparently
- writes code w/o bugs and
- "is lothe(sic) to go to a newsgroup"
Very funny, made me day!
)
I see ye are in pain, Most Tender Newbie, so as to yere punishment for
posting, accept yere lashings, walk the gangplank, drink ye Olde
Starbucke's and go see David Wang's contribution to the last thread at
http://www.google.com/groups? as_q=session.timeout&num=20&as_scoring=r&hl=en&ie=ISO-
8859-
1&btnG=Google+Search&as_epq=iis+6&as_oq=&as_eq=&as_ugroup=
microsoft.public.*&as_usubject=&as_uauthors=&as_umsgid=&lr
=&as_drrb=q&as_qdr=&as_mind=12&as_minm=5&as_miny=1981&as_m
axd=28&as_maxm=7&as_maxy=2003&safe=images
which is significant enough to paste here:
w> I think you're observing the application "idle" recycling happening
in the
w> back ground, which resets all state that is not otherwise persisted.
By
w> default, if you make a request to some application of IIS, if you do
not
w> make another request to that application within 15 minutes, that
application
w> is going to recycle and remove itself from memory, losing any session
state,
w> app state, etc -- everything -- that is not otherwise persisted
(there are
w> ASP-based session state products that would overcome this as well as
provide
w> scale-out abilities).
w>
w> Situations where you'll see this sort of "disappearing variables"
behavior
w> from ASP are:
w> 1. Your ASP Session timeout of X is greater than the IIS idle timeout
of Y.
w> If you make one request at time 0 and another at time between Y and
X,
w> session state will look lost.
w> 2. Your ASP app does not expect any