It really doesn't matter. If a program is waiting for it's turn at the data files because they are locked by another instance, they are using virtually no CPU time. That is what matters. I think trying to build a que with this type of CGI would only make it more complex than it needs to be, and in the end it's still reading and writing the same exact things. But, in your case, even more. With a CGI, file access is what takes the most processing time. Keep that to the bare minimum, which is hopefully just one file, beyond the lock file, it has to open, use, and close.
There is a trade off in everything, and the trade off with building a que to minimize the number of "waiting" instances on a heavily used CGI app isn't worth the extended processing time using such a strategy would create. Especially when memory and disk size is so cheap, and plentiful on a server.
After years of developing MW's CGI applications in Perl, however, I'm now going to be developing all future features in Cold Fusion on our Win2K server with a Sequel Server back end.
------------------
Dan McClain, Editor
The Mustang Works Magazine
1991 Mustang GT - NOVI Supercharged 377 Stroker
1999 Ford Lightning SVT - Supercharged 5.4L Triton