icewildabeast's Journal: Reducing peformance to increase production?

A very peculiar dilemma came about recently, and I have yet find a decent solution for it. We receive on average about 10,000 fax's a day from a server farm. These fax's are put into a pdf format and given unique names. A .Net program was written, and there is a function that scans a folder for changes and then reports them. The problem is when there are more than 2 file changes per second, the function doesn't always recognize all the changes. The "fastest" solution to implement would to have a script or batch that transfers 1 file at a time and only once per second. This way the server (or .Net) can keep up with it's parsing of changes. All it really is doing is parsing and then archiving into a different folder. Is there someone in this community that knows of some program/batch/script/command line that would allow for such a restriction in file transfers?