G
Gemma M
Hi,
Some time ago, I asked a question concerning slow response when opening a
Word document from an Internet server for the first time. All subsequent
Word document openings were pretty quick. Someone responded, in very
technical language, about SOEs and XCOPY to "prime" the network and caching.
However, despite my gentle prodding, he did not elucidate, or distance
himself from the abstract or the deeply technical. However, he did raise my
hopes that there might be a solution. So here, below, I present my problem,
in the hope that someone can be more specific about a solution.
----
I have an ASP page which generates a XML (wrapped in HTLM) file which
represents a Word document. Then, from the client side of the Internet
connection, I open this newly created document using Word. When first this
process runs, following a machine re-boot, it can take up to a minute to
complete. Thereafter, it takes 3 seconds.
The Word command is something like :
Set objWord = CreateObject("Word.Application")
Set doc = objWord.Documents.Open(http://localhost.service/document.doc)
------
Is it true that the network and caching needs priming? If so, does anyone
know how to "prime" such, or know of any Web pages that might tell me how.
I'm using IIS, under XP, and Word 2000.
Many thanks
Gem
Some time ago, I asked a question concerning slow response when opening a
Word document from an Internet server for the first time. All subsequent
Word document openings were pretty quick. Someone responded, in very
technical language, about SOEs and XCOPY to "prime" the network and caching.
However, despite my gentle prodding, he did not elucidate, or distance
himself from the abstract or the deeply technical. However, he did raise my
hopes that there might be a solution. So here, below, I present my problem,
in the hope that someone can be more specific about a solution.
----
I have an ASP page which generates a XML (wrapped in HTLM) file which
represents a Word document. Then, from the client side of the Internet
connection, I open this newly created document using Word. When first this
process runs, following a machine re-boot, it can take up to a minute to
complete. Thereafter, it takes 3 seconds.
The Word command is something like :
Set objWord = CreateObject("Word.Application")
Set doc = objWord.Documents.Open(http://localhost.service/document.doc)
------
Is it true that the network and caching needs priming? If so, does anyone
know how to "prime" such, or know of any Web pages that might tell me how.
I'm using IIS, under XP, and Word 2000.
Many thanks
Gem