Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.
Solved
Application-level varibale?
Posted on 2002-05-19
I have controller.asp which parses a XML file. All http requests come to the controller.asp with a request type. (i.e All the forms' action attribute is equal to controller.asp in all pages with a hidden parameter for the request type). The controller.asp parses the XML file and based on the reqeuest type, gets a ASP Name from the XML file and transfers request to that ASP. This is the scenario.
In controller.asp, I am using the Microsoft XML DOM component to enable parsing. (Code Below). Since the XML DOM is created in the controller.asp, for every request, the DOM object is created, xml file loaded, parsed and destroyed, which is surely a performance overhead!
I am wondering if I can carry out the first two activities - (i.e Creating the XML DOM object and loading the XML file) once in the start of the application and just use this object in the controller.asp, then I am reducing the object creating and loading XML file overhead for the every request. right? Please let me know your opinions.
If right, I need some help with implementing it.
One way, is in the Application_OnStart eventhandler in global.asa file. I can create a application-level varibable set to the XML DOM object and load the XML file in the application-level variable. I can just use this application-level variable in the controller.asp to parse ! How is this implementation pattern? I have always heard and read that COM objects must not be put in Session. Considering this, can I put the XML DOM object (which is COM object) as a application level variable?
Seeking opinions!
**************************
<%
Dim requestType
Dim xmlDoc
dim NNPObj
dim docElement
dim nodeObj
dim docObj
dim childNode
dim rootNode
dim cNodes
requestType=request.form("
set xmlDoc=server.createobject
xmlDoc.async=false
dim bool
bool=xmlDoc.load(server.ma
set docElement=xmlDoc.document
set cNodes= docElement.childNodes
for each nodeObj in cNodes
set NNPObj =nodeObj.attributes
if NNPObj.getNamedItem("id").
response.write "Request Type: "+ requestType +"<br><hr>"
response.write " <b><u>Model Type</u></b>: "+ NNPObj.getNamedItem("model
if NNPObj.getNamedItem("model
response.write " <b><u>Processing ASP </u></b>: "+ NNPObj.getNamedItem("ASPNa
elseif NNPObj.getNamedItem("model
response.write "<b><u>Component Name</u></b>: "+ NNPObj.getNamedItem("compo
response.write "<b><u>Method Name</u></b> :"+ NNPObj.getNamedItem("metho
response.write "<b><u>Presentation Asp</u></b>: "+ NNPObj.getNamedItem("prese
end if
end if
Next
%>
**************************
XMl File:
<controller>
<action id="getEmployee"
modelType="asp"
ASPName="getEmployee.asp"
/>
<action id="addEmployee"
modelType="asp"
ASPName="addEmployee.asp"
/>
<action id="generateOppurunity"
modelType="com"
componentName="SANGenSoft.
methodName="generateOppuru
presentationAsp="confirmOp
/>
<action id="showOppurunity"
modelType="com"
componentName="SANGenSoft.
methodName="showOppurunity
presentationAsp="showOppur
/>
</controller>
**************************
In controller.asp, I am using the Microsoft XML DOM component to enable parsing. (Code Below). Since the XML DOM is created in the controller.asp, for every request, the DOM object is created, xml file loaded, parsed and destroyed, which is surely a performance overhead!
I am wondering if I can carry out the first two activities - (i.e Creating the XML DOM object and loading the XML file) once in the start of the application and just use this object in the controller.asp, then I am reducing the object creating and loading XML file overhead for the every request. right? Please let me know your opinions.
If right, I need some help with implementing it.
One way, is in the Application_OnStart eventhandler in global.asa file. I can create a application-level varibable set to the XML DOM object and load the XML file in the application-level variable. I can just use this application-level variable in the controller.asp to parse ! How is this implementation pattern? I have always heard and read that COM objects must not be put in Session. Considering this, can I put the XML DOM object (which is COM object) as a application level variable?
Seeking opinions!
**************************
<%
Dim requestType
Dim xmlDoc
dim NNPObj
dim docElement
dim nodeObj
dim docObj
dim childNode
dim rootNode
dim cNodes
requestType=request.form("
set xmlDoc=server.createobject
xmlDoc.async=false
dim bool
bool=xmlDoc.load(server.ma
set docElement=xmlDoc.document
set cNodes= docElement.childNodes
for each nodeObj in cNodes
set NNPObj =nodeObj.attributes
if NNPObj.getNamedItem("id").
response.write "Request Type: "+ requestType +"<br><hr>"
response.write " <b><u>Model Type</u></b>: "+ NNPObj.getNamedItem("model
if NNPObj.getNamedItem("model
response.write " <b><u>Processing ASP </u></b>: "+ NNPObj.getNamedItem("ASPNa
elseif NNPObj.getNamedItem("model
response.write "<b><u>Component Name</u></b>: "+ NNPObj.getNamedItem("compo
response.write "<b><u>Method Name</u></b> :"+ NNPObj.getNamedItem("metho
response.write "<b><u>Presentation Asp</u></b>: "+ NNPObj.getNamedItem("prese
end if
end if
Next
%>
**************************
XMl File:
<controller>
<action id="getEmployee"
modelType="asp"
ASPName="getEmployee.asp"
/>
<action id="addEmployee"
modelType="asp"
ASPName="addEmployee.asp"
/>
<action id="generateOppurunity"
modelType="com"
componentName="SANGenSoft.
methodName="generateOppuru
presentationAsp="confirmOp
/>
<action id="showOppurunity"
modelType="com"
componentName="SANGenSoft.
methodName="showOppurunity
presentationAsp="showOppur
/>
</controller>
**************************
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
8
11 Comments
This is what you should do.
global.asa
===========
<object
id="oPersist"
progid="Microsoft.FreeThre
runat="server"
scope="application"></obje
<script language="VBScript" runat="server">
Sub Application_OnStart()
oPersist.async = False
oPersist.load Server.MapPath("MyInfo.xml
End Sub
</script>
page.asp
========
<%
Dim oXML
'Setting it to the Application Scoped Variable
Set oXML = Application.StaticObjects(
%>
global.asa
===========
<object
id="oPersist"
progid="Microsoft.FreeThre
runat="server"
scope="application"></obje
<script language="VBScript" runat="server">
Sub Application_OnStart()
oPersist.async = False
oPersist.load Server.MapPath("MyInfo.xml
End Sub
</script>
page.asp
========
<%
Dim oXML
'Setting it to the Application Scoped Variable
Set oXML = Application.StaticObjects(
%>
Notes
=====
1. The way you are using XML and the DOM is not going to allow for an optimised performance-oriented outcome. In short, it is a clear abuse of the XML Process.
What will follow is the correct way of using XML to squeeze the most out of performance.
=====
1. The way you are using XML and the DOM is not going to allow for an optimised performance-oriented outcome. In short, it is a clear abuse of the XML Process.
What will follow is the correct way of using XML to squeeze the most out of performance.
MSXML Parser That Should Be Used:
==========================
MSXML Version 3.0 SP 2 (Recommended MSXML Version 4.0)
controller.xsl
===============
<?xml version="1.0" encoding="iso-8859-1"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
<xsl:output method="html" indent="yes" encoding="iso-8859-1" />
<xsl:param name="requestType" />
<xsl:template match="/">
<xsl:apply-templates select="controller/action[
</xsl:template>
<xsl:template match="action">
Request Type: <xsl:value-of select="@id" /><br /><hr />
<xsl:choose>
<xsl:when test="@modelType[ . = 'asp']">
<xsl:call-template name="asp" />
</xsl:when>
<xsl:when test="@modelType[ . = 'com']">
<xsl:call-template name="com" />
</xsl:when>
</xsl:choose>
</xsl:template>
<xsl:template name="asp">
<b><u>Processing ASP</u></b>: <xsl:value-of select="@ASPName" /><br /><hr />
</xsl:template>
<xsl:template name="com">
<b><u>Component Name</u></b>: <xsl:value-of select="@componentName" /><br />
<b><u>Method Name</u></b>: <xsl:value-of select="@methodName" /><br />
<b><u>Presentation Asp</u></b>: <xsl:value-of select="@presentationAsp" /><br /><hr />
</xsl:template>
</xsl:stylesheet>
global.asa
==========
<object id="oTemplate"
progid="Msxml2.XSLTemplate
runat="server"
scope="application"></obje
<object id="oPersist"
progid="Msxml2.FreeThreade
runat="server"
scope="application"></obje
<script language="VBScript" runat="server">
Sub Application_OnStart()
Dim oXSLT
Set oXSLT = Server.CreateObject("Msxml
oXSLT.async = False
oXSLT.load Server.MapPath("controller
Set oTemplate.stylesheet = oXSLT
Set oXSLT = Nothing
oPersist.async = False
oPersist.load Server.MapPath("controller
End Sub
</script>
page.asp
========
<%@language="VBScript"%>
<%
On Error Resume Next
Dim oTemplate, oProc, oPersist
Set oTemplate = Application.StaticObjects(
'get the IXSLProcessor whose rental model
'is suited for the application scope
Set oProc = oTemplate.createProcessor(
Set oPersist = Application.StaticObject("
With oProc
.input = oPersist
.addParameter "requestType",Request("req
.transform()
Response.Write(.output)
End With
Set oProc = Nothing
Set oPersist = Nothing
Set oTemplate = Nothing
%>
==========================
MSXML Version 3.0 SP 2 (Recommended MSXML Version 4.0)
controller.xsl
===============
<?xml version="1.0" encoding="iso-8859-1"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
<xsl:output method="html" indent="yes" encoding="iso-8859-1" />
<xsl:param name="requestType" />
<xsl:template match="/">
<xsl:apply-templates select="controller/action[
</xsl:template>
<xsl:template match="action">
Request Type: <xsl:value-of select="@id" /><br /><hr />
<xsl:choose>
<xsl:when test="@modelType[ . = 'asp']">
<xsl:call-template name="asp" />
</xsl:when>
<xsl:when test="@modelType[ . = 'com']">
<xsl:call-template name="com" />
</xsl:when>
</xsl:choose>
</xsl:template>
<xsl:template name="asp">
<b><u>Processing ASP</u></b>: <xsl:value-of select="@ASPName" /><br /><hr />
</xsl:template>
<xsl:template name="com">
<b><u>Component Name</u></b>: <xsl:value-of select="@componentName" /><br />
<b><u>Method Name</u></b>: <xsl:value-of select="@methodName" /><br />
<b><u>Presentation Asp</u></b>: <xsl:value-of select="@presentationAsp" /><br /><hr />
</xsl:template>
</xsl:stylesheet>
global.asa
==========
<object id="oTemplate"
progid="Msxml2.XSLTemplate
runat="server"
scope="application"></obje
<object id="oPersist"
progid="Msxml2.FreeThreade
runat="server"
scope="application"></obje
<script language="VBScript" runat="server">
Sub Application_OnStart()
Dim oXSLT
Set oXSLT = Server.CreateObject("Msxml
oXSLT.async = False
oXSLT.load Server.MapPath("controller
Set oTemplate.stylesheet = oXSLT
Set oXSLT = Nothing
oPersist.async = False
oPersist.load Server.MapPath("controller
End Sub
</script>
page.asp
========
<%@language="VBScript"%>
<%
On Error Resume Next
Dim oTemplate, oProc, oPersist
Set oTemplate = Application.StaticObjects(
'get the IXSLProcessor whose rental model
'is suited for the application scope
Set oProc = oTemplate.createProcessor(
Set oPersist = Application.StaticObject("
With oProc
.input = oPersist
.addParameter "requestType",Request("req
.transform()
Response.Write(.output)
End With
Set oProc = Nothing
Set oPersist = Nothing
Set oTemplate = Nothing
%>
What's going on
===============
1. We can store the stylesheet in application scope directly using the Msxml2.FreeThreadedDOMDocu
2. Microsoft thus, created the IXSLTemplate and IXSLProcessor which is targetted especially in cases such as yours.
3. The problem with your code is that you will have to loop multiple times to do your work in your ASP Code. The XSLT Document takes care of that. More importantly, because of the rental model, it is lightweight. To create the IXSLProcessor, the following must be true.
The stylesheet used must be FreeThreaded. The IXSLTemplate's stylesheet property must be set to that of the FreeThreaded XSLT Document.
4. After getting the the IXSLProcessor, you can then set the input property to that of the Cached XML Document. This way will completely eliminate any I/O processes as every is taking place from memory.
5. By using the XML/XSLT Combination, the ASP code is leaner and meaner.
===============
1. We can store the stylesheet in application scope directly using the Msxml2.FreeThreadedDOMDocu
2. Microsoft thus, created the IXSLTemplate and IXSLProcessor which is targetted especially in cases such as yours.
3. The problem with your code is that you will have to loop multiple times to do your work in your ASP Code. The XSLT Document takes care of that. More importantly, because of the rental model, it is lightweight. To create the IXSLProcessor, the following must be true.
The stylesheet used must be FreeThreaded. The IXSLTemplate's stylesheet property must be set to that of the FreeThreaded XSLT Document.
4. After getting the the IXSLProcessor, you can then set the input property to that of the Cached XML Document. This way will completely eliminate any I/O processes as every is taking place from memory.
5. By using the XML/XSLT Combination, the ASP code is leaner and meaner.
If you do not wish to change your code and want to use the older MSXML Parser, then you just change the global.asa and change the asp code to the following:
<%
Dim szRequestType
Dim oXML
Dim oNode
szRequestType = Request.Form("requestType"
Set oXML = Application.StaticObjects(
Set oNode = oXML.selectSingleNode("/co
If Not oNode Is Nothing Then
Response.Write "Request Type: " & szRequestType & "<br><hr>"
Response.Write "<b><u>Model Type</u><b>: " & oNode.getAttribute("modelT
Select Case oNode.getAttribute("modelT
Case "asp"
Response.Write "<b><u>Processing ASP</u></b>: " & oNode.getAttribute("ASPNam
Case "com"
Response.Write "<b><u>Component Name</u></b>: " & oNode.getAttribute("compon
Response.Write "<b><u>Method Name</u></b>: " & oNode.getAttribute("method
Response.Write "<b><u>Presentation Asp</u></b>: " & oNode.getAttribute("presen
End Select
Set oNode = Nothing
End If
Set oXML = Nothing
%>
<%
Dim szRequestType
Dim oXML
Dim oNode
szRequestType = Request.Form("requestType"
Set oXML = Application.StaticObjects(
Set oNode = oXML.selectSingleNode("/co
If Not oNode Is Nothing Then
Response.Write "Request Type: " & szRequestType & "<br><hr>"
Response.Write "<b><u>Model Type</u><b>: " & oNode.getAttribute("modelT
Select Case oNode.getAttribute("modelT
Case "asp"
Response.Write "<b><u>Processing ASP</u></b>: " & oNode.getAttribute("ASPNam
Case "com"
Response.Write "<b><u>Component Name</u></b>: " & oNode.getAttribute("compon
Response.Write "<b><u>Method Name</u></b>: " & oNode.getAttribute("method
Response.Write "<b><u>Presentation Asp</u></b>: " & oNode.getAttribute("presen
End Select
Set oNode = Nothing
End If
Set oXML = Nothing
%>
by the way the amendment with regard to the controller.xsl, adding the model type display =)
<?xml version="1.0" encoding="iso-8859-1"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
<xsl:output method="html" indent="yes" encoding="iso-8859-1" />
<xsl:param name="requestType" />
<xsl:template match="/">
<xsl:apply-templates select="controller/action[
</xsl:template>
<xsl:template match="action">
Request Type: <xsl:value-of select="@id" /><br /><hr />
Modal Type :<xsl:value-of select="@modelType" /><br /><br />
<xsl:choose>
<xsl:when test="@modelType[ . = 'asp']">
<xsl:call-template name="asp" />
</xsl:when>
<xsl:when test="@modelType[ . = 'com']">
<xsl:call-template name="com" />
</xsl:when>
</xsl:choose>
</xsl:template>
<xsl:template name="asp">
<b><u>Processing ASP</u></b>: <xsl:value-of select="@ASPName" /><br /><hr />
</xsl:template>
<xsl:template name="com">
<b><u>Component Name</u></b>: <xsl:value-of select="@componentName" /><br />
<b><u>Method Name</u></b>: <xsl:value-of select="@methodName" /><br />
<b><u>Presentation Asp</u></b>: <xsl:value-of select="@presentationAsp" /><br /><hr />
</xsl:template>
</xsl:stylesheet>
<?xml version="1.0" encoding="iso-8859-1"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
<xsl:output method="html" indent="yes" encoding="iso-8859-1" />
<xsl:param name="requestType" />
<xsl:template match="/">
<xsl:apply-templates select="controller/action[
</xsl:template>
<xsl:template match="action">
Request Type: <xsl:value-of select="@id" /><br /><hr />
Modal Type :<xsl:value-of select="@modelType" /><br /><br />
<xsl:choose>
<xsl:when test="@modelType[ . = 'asp']">
<xsl:call-template name="asp" />
</xsl:when>
<xsl:when test="@modelType[ . = 'com']">
<xsl:call-template name="com" />
</xsl:when>
</xsl:choose>
</xsl:template>
<xsl:template name="asp">
<b><u>Processing ASP</u></b>: <xsl:value-of select="@ASPName" /><br /><hr />
</xsl:template>
<xsl:template name="com">
<b><u>Component Name</u></b>: <xsl:value-of select="@componentName" /><br />
<b><u>Method Name</u></b>: <xsl:value-of select="@methodName" /><br />
<b><u>Presentation Asp</u></b>: <xsl:value-of select="@presentationAsp" /><br /><hr />
</xsl:template>
</xsl:stylesheet>
to download MSXML3 SP2, go to http://msdn.microsoft.com/xml and click on the right link MSXML3 SP2
if you wish to use MSXML4 SP1, click on the right link and read the install instructions. In the case of MSXML4, the version id should be changed from .3.0 to .4.0 in all cases presented here.
if you wish to use MSXML4 SP1, click on the right link and read the install instructions. In the case of MSXML4, the version id should be changed from .3.0 to .4.0 in all cases presented here.
agrees with b1xml2. It IS the recommended way. although I personally hate the overload of the application. Especially if all xml output is save din the application scope, but that's just me :-/
CJ
CJ
No comment has been added lately and it seems that this question have been abandoned. So it's time to clean up this TA.
I will leave a recommendation in the Cleanup topic area that this question or invite a Moderator to close this question if there's no reply from you after seven days.
In the absence of responses, I will recommend the following:
To accept the comment and points awarded to b1xml2
** PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER **
Just trying to help for the cleanup...
gladxml
I will leave a recommendation in the Cleanup topic area that this question or invite a Moderator to close this question if there's no reply from you after seven days.
In the absence of responses, I will recommend the following:
To accept the comment and points awarded to b1xml2
** PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER **
Just trying to help for the cleanup...
gladxml
Featured Post
Did you know SD-WANs can improve network connectivity? Check out this webinar to learn how an SD-WAN simplified, one-click tool can help you migrate and manage data in the cloud.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
I recently decide that I needed a way to make my pages scream on the net. While searching around how I can accomplish this I stumbled across a great article that stated "minimize the server requests."
I got to thinking, hey, I use more than one…
I was asked about the differences between classic ASP and ASP.NET, so let me put them down here, for reference:
Let's make the introductions...
Classic ASP was launched by Microsoft in 1998 and dynamically generate web pages upon user interact…
Do you want to know how to make a graph with Microsoft Access? First, create a query with the data for the chart. Then make a blank form and add a chart control. This video also shows how to change what data is displayed on the graph as well as form…
How to fix incompatible JVM issue while installing Eclipse
While installing Eclipse in windows, got one error like above and unable to proceed with the installation.
This video describes how to successfully install Eclipse.
How to solve incompa…
Suggested Courses
Course of the Month5 days, 23 hours left to enroll
688 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.