RECYCLING all world-wide app are affected ?

[an]

If an user in Paris intensely use an .asp page

(more than one browser window opened,
simultaneous long search tasks fired,
he uses functions that imply the Cache storaging
by the .asp page...)

the server inevitably recycles the .asp app
and the user can not use the page more
(the searches never complete, cursor-hourglass
still remains in the browser window...)

I'd like to know
if only the bad user in Paris is punished,
and the other good user (in New York, in Rome...)
that were currently using the page can keep to use it
or
all the worl-wide users have their page stopped...

[Mark Fitzpatrick]

If you are referring to classic asp, then you may need to ask the question
in the microsoft.public.inetserver.asp.general newsgroup as this newsgroup
is for ASP.Net.

Typically though, a recycle is done at the application level and not just a
single page. That means that all the pages within an application should be
recycled also. It shouldn't matter where a user is as when an app recycles
it affects the application, and all users, as a whole.

--

Hope this helps,
Mark Fitzpatrick
Former Microsoft FrontPage MVP 199?-2006

"an" <[e-mail] in message
news:0e********************************@4ax.com...

If an user in Paris intensely use an .asp page

(more than one browser window opened,
simultaneous long search tasks fired,
he uses functions that imply the Cache storaging
by the .asp page...)

the server inevitably recycles the .asp app
and the user can not use the page more
(the searches never complete, cursor-hourglass
still remains in the browser window...)

I'd like to know
if only the bad user in Paris is punished,
and the other good user (in New York, in Rome...)
that were currently using the page can keep to use it
or
all the worl-wide users have their page stopped...