I have written a Perl server that acts as a gateway to a MySQL database. When clients connect, the server forks a child (which connects to the db, processes the client's request, disconnects from the db and exits). This works great under LINUX with real processes.
Moving to Windows (2000), I have found that the ActiveState fork emulation (i.e. threads) does not work so well. Once the first client has exited, no other clients can connect. Also, while the first client is connected, no other clients can connect. So, it seems that there is an issue with threads and DBI or DBD-Mysql. I have seen this issues raised on many mailing lists but with no authoritative resolution. Can anyone shed some light on this? Is is DBI or DBD-Mysql? Is it ActiveState Perl? Thanks, Bob __________________________________________________ Do You Yahoo!? Great stuff seeking new owners in Yahoo! Auctions! http://auctions.yahoo.com
