I do’nt have script debugging enabled on IIS 5.1 on XP, but the Classic ASP applications appear to be running in single threaded mode. One page must finish loading before another can load.
Any ideas???
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I do’nt have script debugging enabled on IIS 5.1 on XP, but the Classic ASP applications appear to be running in single threaded mode. One page must finish loading before another can load.
Any ideas???
Mike is right, Classic ASP responses are returned in order of receipt (not simultaneously) when being requested by the same session.
If you need to do two requests at the same time in the same browser (as your web visitors might need to do if say one of the requests is for an image or AJAX) you can disable session state for a page request using
<%@ EnableSessionState=False %>at the top of your ASP page. For more information, see: http://support.microsoft.com/kb/244465When you do this however, you don’t have access to the Session object, so you will need to consider some other way of identifying the user in such pages (e.g. a token on the query string, IP address, custom implemented session state using the Cookie object and a database, etc)
If you aren’t using the Session object at all, it can be disabled in IIS all together, also explained at http://support.microsoft.com/kb/244465