I don't see anything wrong with your idea. In order to make sure a file is
not requested while it is being updated use a "soft lock" scheme to hold off
that request until the file is complete. To do this just keep track of all
the filenames and paths ins a database. Have a flag called Locked and if
that file is being updated by some batch script or whatever set the locked
to "Y" when it's complete set it back to "N". Then when your user makes a
request your ASP checks to make sure the file is not locked etc.
Tim

-----Original Message-----
From: Mick McDonald [mailto:mmcdonald@g...]
Sent: Wednesday, February 27, 2002 6:08 PM
To: Pro ASP HowTo
Subject: [proasp_howto] Database or File storage for XML content


Hi list,

I have a debate here at my company regarding an implementation I would like
to use.

We have an application that allows users to create News articles, Press
Releases, Job Openings, etc...

The data is stored in a SQL 2k DB, which returns XML results when the data
is needed by a page for display.

My thinking is that we could cache the XML after it has been transformed as
HTML as a file on the server, so it can be included or screenscraped as
neeed when called upon, and reduce the load on the server. The files would
then be updated as the DB is updated.

A concern my PM has is that there could be a sharing violation of the cached
files when someone is requesting it, and someone is updating it.

Any one care to comment on this?

Thanks!
Mick McDonald
Developer
http://www.goeveryware.com
mmcdonald@g...
Every://ware
7 N Saginaw #200
Pontiac, MI.
(xxx)xxx-xxxx