C
Chris Hohmann
Responses inline.
I assume they meant that no error is thrown if you attempt to modify the
application object without using lock/unlock. There's a contact link at the
bottom of the page if you'd like to request clarification.
Anthony already gave an example of inconsistent state.
No way to know for sure unless you ask. I don't remember the still present
"endif" allowance.
Use the hit count example without the lock/unlock and send 100 simultaneous
requests.
Evertjan. said:Chris Hohmann wrote on 27 aug 2008 in
microsoft.public.inetserver.asp.general:
One would need to know what they mean by "not need" in this case, Chris.
I assume they meant that no error is thrown if you attempt to modify the
application object without using lock/unlock. There's a contact link at the
bottom of the page if you'd like to request clarification.
How can a state ever be inconsistent?
Anthony already gave an example of inconsistent state.
And I doubt the documentation writers of MS always know what past
implementors did manage to put in the code. Remember the still present
"endif" allowance bug in VBS single line if-else-then?
No way to know for sure unless you ask. I don't remember the still present
"endif" allowance.
The next interesting Q is, how we could ever test this inconsistency,
and more so prove the possible absense of such inconsistency.
Use the hit count example without the lock/unlock and send 100 simultaneous
requests.