File Sytem Object versus MSXML
  Home FAQ Contact Sign in
microsoft.public.inetserver.asp only
 
Advanced search
POPULAR GROUPS

more...

microsoft ... inetserver.asp Profile…
 Up
File Sytem Object versus MSXML         


Author: Edward
Date: Jan 16, 2007 10:04

Hello:

I need to dynamically include documents stored in my own website.
The website is coded in ASP.
As far as I know there are two common options: FSO and the MSXML Objects.
Which one of the two would be less of a resource hog for IIS ? Keep in mind
that the documetns I want to include are stored in the server where the
website resides, not on another webserver. Otherwise I'd have no choice but
to use msxml.

Thanks in advance.

Edward
3 Comments
Re: File Sytem Object versus MSXML         


Author: Anthony Jones
Date: Jan 16, 2007 10:33

"Edward" nowhere.com> wrote in message
news:qs8rh.662035$1T2.29971@pd7urf2no...
> Hello:
>
> I need to dynamically include documents stored in my own website.
> The website is coded in ASP.
> As far as I know there are two common options: FSO and the MSXML Objects.
> Which one of the two would be less of a resource hog for IIS ? Keep in
mind
> that the documetns I want to include are stored in the server where the
> website resides, not on another webserver. Otherwise I'd have no choice
but
> to use msxml.
>

I'm not sure why you would think MSXML would figure in any such solution.
FSO is easy enough to use for standard text content. ADODB.Stream is a more
flexible solution that handles both text and binary content fairly well
Show full article (0.79Kb)
no comments
Re: File Sytem Object versus MSXML         


Author: Dave Anderson
Date: Jan 16, 2007 11:17

Edward wrote:
> I need to dynamically include documents stored in my own
> website. The website is coded in ASP.

Depending on what you mean by "dynamically include", you could include
Server.Execute() or