I'm reasonably confused how Msxml2.ServerXMLHTTP and Microsoft.XMLHTTP work. It seems as if they both call up (load? instantiate? . . . don't know the right word) something called MSXML parser (which comes in various versions on the server) which then processes the target page and sends the HTML output back to the browser. Is that halfway accurate?
If they are both calling up the same MSXML parser, then what difference does it make if we use Msxml2.ServerXMLHTTP or Microsoft.XMLHTTP? Or do they call different versions of the parser?
The documentation I referred to was specifically for Msxml2.ServerXMLHTTP, so I don't see how Msxml2.ServerXMLHTTP solves the threading issue.
And finally, what is going on at the browser level? It seems that there are differences in how the returned info is handled by the browser.
hmmm, where is your data that seems to take forever,
Sql, access, mysql, oracle??
my suggestion would be to try and get a simple flat table that is fast to get the detail from, this can all be pre compiled so all you're doing is accessing one record with all required fields in.
Then run some form of update for this table, if in sql, mysql or oracle you can run scheduled procedures to collect the required info and update the page record!!!
Not sure if that helps in any way!! just means that theres no virus issue or anything and just a simple retreival of one record shouldn't slow everything down!!
I needn't to do anything, just type in the code in a text file and then save it to a folder. A few minutes later I got the virus alert and gave me the option to delete that text file!!
I found as long as I include both Server.CreateObject("Microsoft.XMLHTTP") and Server.CreateObject("Scripting.FileSystemObject") stuff, the alert happens!
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.