If your data files aren't too big, there shouldn't be a problem.
Technically, only one person can access the files at a time, which sounds really bad. In practical terms, though, it shouldn't cause any problem, because access to the files only lasts a fraction of a second. When any command is sent to db.cgi, the program starts, the files are accessed and read or written, data for a new webpage is sent to the browser, and the program ends. While one person is looking at the data he just searched for, the program is no longer running for him at all, but is available for someone else to use.
If your files get to be big -- a Meg or more -- searches will noticeably slow down and users may end up in a queue.
JPD
----------------------------------------------------
JPDeni's DBMan-ual
How to ask questions the smart way.
Technically, only one person can access the files at a time, which sounds really bad. In practical terms, though, it shouldn't cause any problem, because access to the files only lasts a fraction of a second. When any command is sent to db.cgi, the program starts, the files are accessed and read or written, data for a new webpage is sent to the browser, and the program ends. While one person is looking at the data he just searched for, the program is no longer running for him at all, but is available for someone else to use.
If your files get to be big -- a Meg or more -- searches will noticeably slow down and users may end up in a queue.
JPD
----------------------------------------------------
JPDeni's DBMan-ual
How to ask questions the smart way.