为什么传统的ASP脚本或请求为每个客户端运行顺序 [英] why classic asp scripts or requests run sequentially for each client

查看:78
本文介绍了为什么传统的ASP脚本或请求为每个客户端运行顺序的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我注意到,很多次,我不知道为什么它的工作原理是这样

I have noticed that so many times, and i don't know why it works like this

在这个例子:
它是所有ASP编写的,在缓冲,IIS 7,运营商级服务器,充满了RAM和CPU

for this example : it is all written in asp, buffering on, IIS 7, carrier class server, full of RAM and CPU

正如你可以看到捕捉,第一主页执行,那么3 AJAX脚本调用,使用jQuery。

As you can see on capture, first the main page is executed, then 3 ajax scripts are called, with Jquery.

我不得不打电话的document.ready事件之前,第一个,使其成为2在别人面前的答案。

I had to call the first one before document.ready event to make it answers before the 2 others.

否则,如果3被称为同时,它们将不会直到最慢的完成执行得到答案。
2流芳百世被称为在的document.ready。我们清楚地看到,当最慢的执行是在2开始作出反应。但最轻的之一将是非常快的孤独,有些毫秒。

Otherwise, if the 3 are called at the same time, they won't get answer until the slowest one has finished executing. The 2 lasts are called at document.ready. We clearly see that the 2 start to respond when execution of the slowest one is over. But the lightest one would be very fast alone, some ms.

这发生得,当我从应用程序中下载一些文件。该应用程序使用bynarystream方法发送的文件。当一个文件从浏览器客户端下载,应用程序不会回答任何其他浏览器请求(我的意思是比如另一个标签),直至下载完成。

This happens too when i download some files from the app. The app sends files using bynarystream method. When a file is downloaded from a browser client, app wont answer to any other browser request(I mean in another tab for example) until download is finished.

但奇怪的是,你可以打开另一个浏览器(IE,Chrome浏览器...),服务器将立即回答任何要求,但会采取同样为这个新的浏览器。从这个浏览器没有请求可以并行运行。

The strange thing is that you can open another browser (IE, Chrome...) and the server will answer any request immediately, but will act the same for this new browser. No requests from this browser can be run in parallel.

我知道ASP是一种古老的东西,但有人可以告诉我为什么是这样的?

I know ASP is a old stuff, but can somebody tell me why it works like this ?

这是由于浏览器的限制或技术?由于会话机制?由于IIS?由于数据库访问(我相信没有因为流媒体内容下载时不涉及数据库访问)?
它会以另一种方式为别人打工的语言和环境?

Is it due to browser limitations or technology? due to session mechanism? due to IIS ? due to database accesses (I believe no because downloads don't involve DB access when streaming content) ? Would it work in another way for others languages and environment ?

我可以改变这种行为?怎么样?

Can i change this behavior ? How ?

干杯

弗雷德

推荐答案

尝试和GetListeDossier.asp禁用会议,我会期待你的其他请求将与此页面同时运行...

Try and disable sessions for GetListeDossier.asp and I would expect your other requests will run concurrently with this page...

会话使用会话只能得到按顺序处理单线程的,因此页面。

Sessions are single threaded and hence pages using sessions can only get processed sequentially.

这篇关于为什么传统的ASP脚本或请求为每个客户端运行顺序的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆