对ASP，“会话”以及多个请求的排队感到困惑 [英] Confused about ASP, "sessions", and queuing of multiple requests

问题描述

我正在试图理解ASP似乎是阻塞的情况。

"排队"要求。这是在带有IIS5的Win2K高级服务器上。


我看过一些帖子（例如，
http：/ /groups.google.com/groups?hl=e...ngxa06.phx.gbl ）

表示当ASP进入

相同的会话。


我的第一个问题是有人可以确认这是真的吗？ （见下文）。


我的第二个问题是关于什么是同一会话。在这种情况下意味着什么？


我在排队时看到的一些帖子只是说

会话，但是我还看到一些帖子说ASP会话，其中

特别提到ASP会话对象。后一个参考（ASP

会话对象）更精确，但我的测试（再次，见下文）似乎

表示对会话的这种解释;不是ASP会话对象。


这是尝试的测试：


1）我从ServerObjects安装了Waitfor

（ http://www.serverobjects.com/ products.htm），并在c：\中创建了一个小的text.txt

文件。


2）我把Waitfor.asp在我的网站上。


3）我运行了性能监视器，并添加了请求排队。柜台


4）使用IE浏览器，我去了 http：/ /myserver/waitfor.asp


5）连接后，我开始点击IE刷新按钮

点击IE刷新按钮，我可以在性能监视器中看到请求排队

计数器攀升。


以上测试SEEM至少表明ASP将*不良*只处理

a来自IE的单一请求，即ASP * IS *排队，但我仍然感到困惑，在这种情况下这种排队将会发生什么情况（什么呢？）

会话在这种情况下意味着什么？）。


有人可以澄清这个吗？


谢谢，并且对于交叉帖子和稍长的帖子道歉...

Hi,

I''m trying to understand a situation where ASP seems to be "blocking" of
"queuing" requests. This is on a Win2K Advanced Server, with IIS5.

I''ve seen some posts (e.g.,
http://groups.google.com/groups?hl=e...ngxa06.phx.gbl)
that indicate that ASP will queue up requests when they come in with the
same "session".

My first question is "Can someone confirm that this is true?" (see below).

My second is regarding what "same session" means in this context?

Several of the posts that I''ve seen with respect to this queuing just say
"session", but I''ve also seen some posts that say "ASP session", and which
specifically mention "the ASP Session object". This latter reference ("ASP
Session object") is more precise, but my testing (again, see below) seems to
indicate that this interpretation of "session" is not "ASP Session object".

Here''s the test that tried:

1) I installed the Waitfor from ServerObjects
(http://www.serverobjects.com/products.htm), and created a small "text.txt"
file in c:\.

2) I put Waitfor.asp in my website.

3) I ran Performance Monitor and added the "Requests Queued" counter

4) Using IE, I went to http://myserver/waitfor.asp

5) Once it connected, I started clicking the IE Refresh button
As I clicked the IE Refresh button, I could see the "Requests Queued"
counter climb in Performance Monitor.

The above test SEEM to at least indicate that ASP will *INDEED* only process
a single request from IE, i.e., that ASP *IS* queuing, but I''m still
confused about under what circumstances this queuing will happen (what does
"session" mean in this context?).

Can someone clarify this?

Thanks, and apologies for both the cross-post and somewhat long post...

推荐答案

自从IIS 3.0以来，这是真的不需要

快速刷新看看它的实际效果。


例如，当IE同时向IIS发送
请求时，这是必要的。例如，当您使用

分割页面时，框架集：每个框架包含一个HTML页面作为其源。刷新一个

框架集然后需要向服务器询问多个HTML页面。


另一个例子是当objet的源是一个ASP页面时，像这样：


< img src =" get_the_image.asp">


使用Javascript和其他高级设施从一个或多个ASP页面请求数据

也增加了对Web服务器同时发出多个
请求的可能性。从这些示例中可以清楚地看出，服务器无法并行运行这些请求，因为这些页面中的代码可能会产生矛盾。

更改为会话变量，全局变量和/或其他对象，例如

后端对SQL-Server的请求。这应该清除你对

心灵的任何困惑。


顺便说一句，使用像WaitFor和其他objets这样的东西在ASP中定时

可能会导致IIS的性能严重下降，并且必须在必要时保留它们的b $ b用法。


SL


" Ohaya" < Ohaya@NO_SPAM.cox.net>在消息中写道

news：u0 *************** @ TK2MSFTNGP11.phx.gbl ...

That''s true since IIS 3.0 and there are occasions when you don''t need to
make quick refresh to see it in action.

For example, this is necessary when the IE is making simultaneous requests
to the IIS. Exemple of this are when you are dividing your page using
Frameset: each frame contains one HTML page as its source. Refreshing a
frameset then require to ask the server for more than one HTML page.

Another example is when the source of an objet is an ASP page, like this:

<img src="get_the_image.asp">

The use of Javascript and of other advanced facilities for requesting data
from one or more ASP pages also rise the possibilities of having multiple
simultaneous requests to the web server. It is clear from those example
that the server cannot run these requests in parallele because of the
possibility that the codes inside theses pages can make contradictory
changes to Session variables, global variables and/or other objects, like
backend requests to a SQL-Server. This should clear any confusion into your
mind.

By the way, using things like WaitFor and others objets for timing in ASP
can result in a severe degradation of performance from the IIS and their
usages must be reserved to the cases when they are strictly necessary.

S. L.

"Ohaya" <Ohaya@NO_SPAM.cox.net> wrote in message
news:u0***************@TK2MSFTNGP11.phx.gbl...

我正在试图理解ASP似乎是阻塞的情况。
排队要求。这是在带有IIS5的Win2K高级服务器上。

我看过一些帖子（例如，
http://groups.google .com / groups？hl = e ... ngxa06.phx.gbl ）表示ASP会在进入
相同的会话时排队请求。
<我的第一个问题是有人能证实这是真的吗？ （见下文）。

我的第二个问题是关于什么是同一会话。在这种情况下意味着什么呢？

关于这个排队的几个帖子只是说
session，但我也看过一些帖子说的ASP会话，并且具体提到ASP会话对象。后一个参考
（ASP会话对象）更精确，但我的测试（再次，见下文）似乎是
来表示对会话的这种解释。不是ASP Session
object。
这是尝试的测试：

1）我从ServerObjects安装了Waitfor
（ http://www.serverobjects.com/products.htm) ，并创建了一个小
" text.txt"文件在c：\。

2）我把Waitfor.asp放在我的网站上。

3）我运行了性能监视器并添加了请求排队。柜台

4）使用IE浏览器，我去了 http：// myserver / waitfor .asp

5）连接后，我开始点击IE刷新按钮

当我点击IE刷新按钮时，我可以看到请求在性能监视器中排队
计数器爬升。

以上测试SEEM至少表明ASP将* INDEED *仅
处理来自IE的单个请求，即该ASP * IS *排队，但我仍然对这种排队将会发生什么情况感到困惑（在这种情况下，
的会话是什么意思？）。

有人可以澄清这一点吗？

谢谢，并为交叉帖子和稍长的帖子道歉......

Hi,

I''m trying to understand a situation where ASP seems to be "blocking" of
"queuing" requests. This is on a Win2K Advanced Server, with IIS5.

I''ve seen some posts (e.g.,
http://groups.google.com/groups?hl=e...ngxa06.phx.gbl) that indicate that ASP will queue up requests when they come in with the
same "session".

My first question is "Can someone confirm that this is true?" (see below).

My second is regarding what "same session" means in this context?

Several of the posts that I''ve seen with respect to this queuing just say
"session", but I''ve also seen some posts that say "ASP session", and which
specifically mention "the ASP Session object". This latter reference ("ASP Session object") is more precise, but my testing (again, see below) seems to indicate that this interpretation of "session" is not "ASP Session object".
Here''s the test that tried:

1) I installed the Waitfor from ServerObjects
(http://www.serverobjects.com/products.htm), and created a small "text.txt" file in c:\.

2) I put Waitfor.asp in my website.

3) I ran Performance Monitor and added the "Requests Queued" counter

4) Using IE, I went to http://myserver/waitfor.asp

5) Once it connected, I started clicking the IE Refresh button
As I clicked the IE Refresh button, I could see the "Requests Queued"
counter climb in Performance Monitor.

The above test SEEM to at least indicate that ASP will *INDEED* only process a single request from IE, i.e., that ASP *IS* queuing, but I''m still
confused about under what circumstances this queuing will happen (what does "session" mean in this context?).

Can someone clarify this?

Thanks, and apologies for both the cross-post and somewhat long post...

Sylvain，


感谢您的回复...


Re。等等，我刚刚为我描述的测试安装了它。


对不起，如果我是钝的。我想我明白一个IE实例可以向IIS生成多个HTTP请求，例如，在你描述的
的实例中。在我们的例子中，我认为你将IMG SRC设置为

ASP的例子正是我们所拥有的，在一个页面上有多个这些IMG。


但是，我想我还不清楚IIS / ASP何时会或者不会在排队中处理这些多个请求。时尚而不是排队时尚。


究竟是什么决定了这一点？正如我所提到的那样，我在同一会话中隐约地看到了这些帖子，而没有明确界定它们的含义。

会话。


实际上，我追逐所有这些的原因是我们在多处理器服务器上运行IIS是
。随着IE客户端向IIS发出多个

请求，我们认为来自IE的多个请求将分布在多个处理器上。


但是在我们的生产服务器上，对于

IE /客户端的给定用户操作，再次向IIS创建了几个HTTP请求，我们是

在1个CPU上查看CPU活动，然后是下一个CPU，然后是下一个CPU等等，直到用户操作完成后才需要
。


我们得出的结论是，由于某种原因，生产服务器上的ASP并不处理多个请求并行，而是

对请求进行排队（我们看到在我们用于测试的不同的
多处理器服务器上进行并行处理，但不在生产

机器上）。


我们无法弄清楚这两台机器之间有什么不同，因为
会导致请求排队案件，但不在另一个。


谢谢，

吉姆


" Sylvain Lafontaine" < sylvain aei ca（填空，请不要发送垃圾邮件）>

在消息新闻中写道：O7 *************** @ tk2msftngp13.phx。 gbl ...

Sylvain,

Thanks for responding...

Re. Waitfor, I just installed it for the test I described.

Sorry if I''m being obtuse. I think I understand that one IE instance can
generate multiple HTTP requests into IIS, e.g., in the instances that you
described. In our case, I think your example of setting an IMG SRC to an
ASP is exactly what we have, with multiple of these IMGs on one page.

But, I guess I''m still unclear about when IIS/ASP will or will not handle
these multiple requests in a "queuing" fashion vs. not in a queuing fashion.

What exactly determines this? As I mentioned, the posts I''ve seen vaguely
mention "in the same session", without clearly defining what they mean by a
"session".

Actually, the reason that I''m chasing all of this around is that we are
running IIS on a multiprocessor server. With the IE client firing multiple
requests to IIS, we thought that the multiple requests from IE would be
spread across the multiple processors.

But on our production server, instead, for a given user operation at the
IE/client end, which, again, creates several HTTP requests to IIS, we''re
seeing CPU activity on 1 CPU, then the next CPU, then the next CPU, etc.,
until the user operation is complete.

The conclusion we''re coming to is that for some reason ASP on the production
server is not handling the multiple requests "in parallel", but rather
queuing the requests (we see the parallel processing on a different
multiprocessor server that we use for testing, but not on the production
machine).

We just cannot figure out what is different between these 2 machines that
would cause queuing the requests in one case, but not in the other.

Thanks,
Jim

"Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)>
wrote in message news:O7***************@tk2msftngp13.phx.gbl...

自IIS 3.0以来这是真的，有时候你不需要快速刷新才能看到它的实际效果。
<例如，当IE同时向IIS发出请求时，这是必要的。例如，当您使用
框架分割页面时：每个框架包含一个HTML页面作为其来源。刷新一个
框架集然后需要向服务器询问多个HTML页面。

另一个例子是objet的源是一个ASP页面，如下所示：

< img src =" get_the_image.asp">

使用Javascript和其他先进设施从一个或多个ASP页面请求数据也增加了可能性同时向Web服务器发出多个请求。从这些示例中可以清楚地看出，服务器无法并行运行这些请求，因为这些页面内的代码可能会对Session变量，全局变量和/或变量产生矛盾的变化。其他对象，例如对SQL-Server的后端请求。这应该可以清除你脑海里的任何混乱。

顺便说一下，使用像WaitFor和其他人那样在ASP中定时的东西可能会导致性能严重下降。 IIS和他们的用法必须保留在严格必要的情况下。

SL

Ohaya < Ohaya@NO_SPAM.cox.net>在消息中写道
新闻：u0 *************** @ TK2MSFTNGP11.phx.gbl ...

That''s true since IIS 3.0 and there are occasions when you don''t need to
make quick refresh to see it in action.

For example, this is necessary when the IE is making simultaneous requests
to the IIS. Exemple of this are when you are dividing your page using
Frameset: each frame contains one HTML page as its source. Refreshing a
frameset then require to ask the server for more than one HTML page.

Another example is when the source of an objet is an ASP page, like this:

<img src="get_the_image.asp">

The use of Javascript and of other advanced facilities for requesting data
from one or more ASP pages also rise the possibilities of having multiple
simultaneous requests to the web server. It is clear from those example
that the server cannot run these requests in parallele because of the
possibility that the codes inside theses pages can make contradictory
changes to Session variables, global variables and/or other objects, like
backend requests to a SQL-Server. This should clear any confusion into your mind.

By the way, using things like WaitFor and others objets for timing in ASP
can result in a severe degradation of performance from the IIS and their
usages must be reserved to the cases when they are strictly necessary.

S. L.

"Ohaya" <Ohaya@NO_SPAM.cox.net> wrote in message
news:u0***************@TK2MSFTNGP11.phx.gbl...

排队要求。这是在带有IIS5的Win2K高级服务器上。

我看过一些帖子（例如，

Hi,

I''m trying to understand a situation where ASP seems to be "blocking" of
"queuing" requests. This is on a Win2K Advanced Server, with IIS5.

I''ve seen some posts (e.g.,

http：/ /groups.google.com/groups?hl=e...ngxa06.phx.gbl ）

表示ASP将在何时排队请求他们进入相同的会话。

我的第一个问题是有人能证实这是真的吗？ （参见下面的
）。
我的第二个问题是关于什么是同一会话。在这种情况下意味着什么呢？

我已经看到的关于这个排队的几个帖子只是
说会话，但我也看过一些帖子说的ASP session和
，具体提到ASP Session对象。后一个引用

that indicate that ASP will queue up requests when they come in with the
same "session".

My first question is "Can someone confirm that this is true?" (see below).
My second is regarding what "same session" means in this context?

Several of the posts that I''ve seen with respect to this queuing just say "session", but I''ve also seen some posts that say "ASP session", and which specifically mention "the ASP Session object". This latter reference

（ASP

("ASP

Session对象）更精确，但我的测试（再次，见下文）

Session object") is more precise, but my testing (again, see below)

似乎

seems to

表明这种对会话的解释。不是ASP Session

indicate that this interpretation of "session" is not "ASP Session

object。

object".

这是尝试的测试：

1）我安装了来自ServerObjects的Waitfor
（ http://www.serverobjects.com/ products.htm），并在c：\中创建了一个小的

Here''s the test that tried:

1) I installed the Waitfor from ServerObjects
(http://www.serverobjects.com/products.htm), and created a small

" text.txt"

"text.txt"

文件。

2）我把Waitfor.asp放在我的网站上。

3）我运行了性能监视器，并添加了请求排队。柜台

4）使用IE浏览器，我去了 http：// myserver / waitfor .asp

5）连接后，我开始点击IE刷新按钮

当我点击IE刷新按钮时，我可以看到请求在性能监视器中排队
反击。

以上测试SEEM至少表明ASP将* INDEED *仅

file in c:\.

2) I put Waitfor.asp in my website.

3) I ran Performance Monitor and added the "Requests Queued" counter

4) Using IE, I went to http://myserver/waitfor.asp

5) Once it connected, I started clicking the IE Refresh button
As I clicked the IE Refresh button, I could see the "Requests Queued"
counter climb in Performance Monitor.

The above test SEEM to at least indicate that ASP will *INDEED* only

进程

来自IE的一个请求，即ASP * IS *排队，但我仍然对这种排队将在什么情况下发生的事情感到困惑（

a single request from IE, i.e., that ASP *IS* queuing, but I''m still
confused about under what circumstances this queuing will happen (what

会话在这种情况下是什么意思？）。

有人可以澄清一下这个吗？

谢谢，并对这些交叉帖子和有点长的道歉发布...

"session" mean in this context?).

Can someone clarify this?

Thanks, and apologies for both the cross-post and somewhat long post...

Sylvain，


BTW ，我忘了提一下：


如果我用2个不同的IE实例运行我的Waitfor测试（在同一台机器上，

但是第二个IE从Start开始，而不是使用Ctrl-N）同时，我看到了

请求在Perfmon中执行为2，即在这种情况下，IIS * IS *

显然同时/并行处理这两个请求。


就像我说的那样，我对上面测试的

与从单个IE生成多个HTTP请求之间的不同（具体）感到困惑

实例......


Ohaya < Ohaya@NO_SPAM.cox.net>在消息中写道

新闻：Oi **************** @ TK2MSFTNGP11.phx.gbl ...

Sylvain,

BTW, I forgot to mention:

If I run my Waitfor test with 2 different instances of IE (on same machine,
but 2nd IE started from Start, not using Ctrl-N) simultaneously, I see
Requests Executing in Perfmon as 2, i.e., in this situation, IIS *IS*
apparently processing both requests simultaneously/in parallel.

Like I said, I''m confused about what is different (specifically) between the
above test, and generating multiple HTTP requests from a single IE
instance...

"Ohaya" <Ohaya@NO_SPAM.cox.net> wrote in message
news:Oi****************@TK2MSFTNGP11.phx.gbl...

Sylvain，

感谢您的回复...

Re。等等，我刚刚为我描述的测试安装了它。

抱歉，如果我迟钝了。我想我明白，一个IE实例可以向IIS生成多个HTTP请求，例如，在您描述的实例中。在我们的例子中，我认为你将IMG SRC设置为ASP的例子正是我们所拥有的，在一个页面上有多个这些IMG。

但是，我想我是''我还不清楚IIS / ASP何时会或者不会在排队中处理这些多个请求。时尚而不是排队的
时尚。
究竟是什么决定了这一点？正如我所提到的那样，我在同一会话中隐约地提到的帖子没有明确定义b $ ba会话的含义。

实际上，我追逐所有这些的原因是我们在多处理器服务器上运行IIS。随着IE客户端向IIS发送
多个请求，我们认为来自IE的多个请求将分布在多个处理器上。

但是在我们的生产服务器上，相反，对于IE /客户端的给定用户操作，再次向IIS创建多个HTTP请求，我们在1个CPU上看到CPU活动，然后是下一个CPU，然后是下一个CPU CPU等等，直到用户操作完成。

我们得出的结论是，由于某种原因，
生产服务器上的ASP没有处理多个请求并行，而是排队请求（我们在不同的多处理器服务器上看到并行处理，我们用于测试，但不在生产机器上）。

我们无法弄清楚这两台机器之间的区别是什么？
会导致请求在一个案例中排队，而在另一个案例中则不会。

谢谢，
吉姆

Sylvain Lafontaine < sylvain aei ca（填空，请不要发送垃圾邮件）>
写在留言新闻中：O7 *************** @ tk2msftngp13.phx.gbl ...

Sylvain,

Thanks for responding...

Re. Waitfor, I just installed it for the test I described.

Sorry if I''m being obtuse. I think I understand that one IE instance can
generate multiple HTTP requests into IIS, e.g., in the instances that you
described. In our case, I think your example of setting an IMG SRC to an
ASP is exactly what we have, with multiple of these IMGs on one page.

But, I guess I''m still unclear about when IIS/ASP will or will not handle
these multiple requests in a "queuing" fashion vs. not in a queuing fashion.
What exactly determines this? As I mentioned, the posts I''ve seen vaguely
mention "in the same session", without clearly defining what they mean by a "session".

Actually, the reason that I''m chasing all of this around is that we are
running IIS on a multiprocessor server. With the IE client firing multiple requests to IIS, we thought that the multiple requests from IE would be
spread across the multiple processors.

But on our production server, instead, for a given user operation at the
IE/client end, which, again, creates several HTTP requests to IIS, we''re
seeing CPU activity on 1 CPU, then the next CPU, then the next CPU, etc.,
until the user operation is complete.

The conclusion we''re coming to is that for some reason ASP on the production server is not handling the multiple requests "in parallel", but rather
queuing the requests (we see the parallel processing on a different
multiprocessor server that we use for testing, but not on the production
machine).

We just cannot figure out what is different between these 2 machines that
would cause queuing the requests in one case, but not in the other.

Thanks,
Jim

"Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)>
wrote in message news:O7***************@tk2msftngp13.phx.gbl...

自IIS 3.0以来，这是真的，有时候你不需要快速刷新才能看到它的实际效果。

例如，当IE同时向IIS发出
请求

That''s true since IIS 3.0 and there are occasions when you don''t need to
make quick refresh to see it in action.

For example, this is necessary when the IE is making simultaneous requests

时，这是必要的。例如，当您使用
框架分割页面时：每个框架包含一个HTML页面作为其来源。刷新一个
框架然后需要向服务器询问多个HTML页面。

另一个例子是objet的源是一个ASP页面，比如
这个： br />< img src =" get_the_image.asp">

使用Javascript和其他高级工具从一个或多个ASP页面请求
数据也增加了可能性同时向Web服务器发送
多个请求。从这些示例中可以清楚地看出，服务器无法并行运行这些请求，因为这些页面内的代码可能会对Session变量，全局变量和/或变量产生矛盾的变化。其他对象，
类似于对SQL-Server的后端请求。这应该清除任何混淆

to the IIS. Exemple of this are when you are dividing your page using
Frameset: each frame contains one HTML page as its source. Refreshing a
frameset then require to ask the server for more than one HTML page.

Another example is when the source of an objet is an ASP page, like this:
<img src="get_the_image.asp">

The use of Javascript and of other advanced facilities for requesting data from one or more ASP pages also rise the possibilities of having multiple simultaneous requests to the web server. It is clear from those example
that the server cannot run these requests in parallele because of the
possibility that the codes inside theses pages can make contradictory
changes to Session variables, global variables and/or other objects, like backend requests to a SQL-Server. This should clear any confusion into

你的

介意。

顺便说一句，使用像WaitFor和其他objets这样的东西来定时
ASP可能会导致IIS的性能严重下降，并且必须在必要时保留它们的用法。

SL

; Ohaya" < Ohaya@NO_SPAM.cox.net>在消息中写道
新闻：u0 *************** @ TK2MSFTNGP11.phx.gbl ...

mind.

By the way, using things like WaitFor and others objets for timing in ASP can result in a severe degradation of performance from the IIS and their
usages must be reserved to the cases when they are strictly necessary.

S. L.

"Ohaya" <Ohaya@NO_SPAM.cox.net> wrote in message
news:u0***************@TK2MSFTNGP11.phx.gbl...

的排队要求。这是在带有IIS5的Win2K高级服务器上。

我看过一些帖子（例如，

Hi,

I''m trying to understand a situation where ASP seems to be "blocking" of "queuing" requests. This is on a Win2K Advanced Server, with IIS5.

I''ve seen some posts (e.g.,

http://groups.google.com/groups?hl=e...ngxa06.phx.gbl ）

表示ASP将排队请求时他们用相同的会话来获得
。

我的第一个问题是有人能证实这是真的吗？ （见下文）。
我的第二个问题是关于什么是同一会话。在这种情况下意味着什么呢？

我在这个排队中看到的一些帖子只是说会话，但我也看过一些帖子说ASP会话 ;，并且具体提到ASP会话对象。后一个引用

that indicate that ASP will queue up requests when they come in with the same "session".

My first question is "Can someone confirm that this is true?" (see below).
My second is regarding what "same session" means in this context?

Several of the posts that I''ve seen with respect to this queuing just say "session", but I''ve also seen some posts that say "ASP session", and which specifically mention "the ASP Session object". This latter reference

（ASP

("ASP

Session对象）更精确，但我的测试（再次，见下文）

Session object") is more precise, but my testing (again, see below)

to

表示对session的这种解释。不是ASP Session

indicate that this interpretation of "session" is not "ASP Session

object。

object".

这是尝试的测试：

1）我安装了来自ServerObjects的Waitfor
（ http://www.serverobjects.com/ products.htm），并在c：\中创建了一个小的

Here''s the test that tried:

1) I installed the Waitfor from ServerObjects
(http://www.serverobjects.com/products.htm), and created a small

" text.txt"

"text.txt"

文件。

2）我把Waitfor.asp放在我的网站上。

3）我运行了性能监视器，并添加了请求排队。柜台

4）使用IE浏览器，我去了 http：// myserver / waitfor .asp

5）连接后，我开始点击IE刷新按钮

当我点击IE刷新按钮时，我可以看到请求在性能监视器中排队
反击。

以上测试SEEM至少表明ASP将* INDEED *仅

file in c:\.

2) I put Waitfor.asp in my website.

3) I ran Performance Monitor and added the "Requests Queued" counter

4) Using IE, I went to http://myserver/waitfor.asp

5) Once it connected, I started clicking the IE Refresh button
As I clicked the IE Refresh button, I could see the "Requests Queued"
counter climb in Performance Monitor.

The above test SEEM to at least indicate that ASP will *INDEED* only

进程

来自IE的一个请求，即ASP * IS *排队，但我仍然对这种排队将在什么情况下发生的事情感到困惑（

a single request from IE, i.e., that ASP *IS* queuing, but I''m still
confused about under what circumstances this queuing will happen (what

会话在这种情况下是什么意思？）。

有人可以澄清一下这个吗？

谢谢，并对这些交叉帖子和有点长的道歉
post ...

"session" mean in this context?).

Can someone clarify this?

Thanks, and apologies for both the cross-post and somewhat long post...

这篇关于对ASP，“会话”以及多个请求的排队感到困惑的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！