General question about persistence

[Neil Gould]

Hi Anthony,

Thanks to the various responses to my questions, I am getting a clearer
notion of how the asp.dll "sees" a "page".

Note that effectively anything between %> <% (that is anything outside of
the script delimiters) effectively becomes a Response.BinaryWrite which
sends the bytes found between a closing %> and an opening <%. The parser
having replaced %> <% and anything in between with such a psuedo binarywrite
now has pure script that it can parse. (Actually its a little more complex
than that but its a good working mental model).

OK. That would explain a lot.

Once the request processing is completed the Script context is reset
including the ScriptTimeout, the only data that can persist beyond that is
Session and Application.

AHA!

Thanks, as this is consistent with what I've observed, but I haven't seen
explained anywhere. I think I've got it now.

Best,

Neil

 

[Neil Gould]

Hi all,

Bob Barrows [MVP] wrote on 22 jul 2008 in
microsoft.public.inetserver.asp.general:

Hi,

[...]
And the ASP-engine could be instructed to do serverside things
unrelated to the rendered content, like manipulating Session or
Application variables using ASP statements, and like file
manipulation, database manipulation or sending an email, all using
specific ASP-external components.

This is the aspect that I'm dealing with most often in trying to get a
handle on persistence issues. Sometimes, variable values that aren't
stored as session items get "lost", and are reported as empty when
tested with response.write or some other means.

Show us.

Indeed. Show us an example.

I'll try to come up with a compact example.

Neil