Mark Hedges wrote: > I see. In that case it would be a problem if two children try > to write the socket at the same time, right?
Exactly. Same problem as forking with an open filehandle. >> I don't believe it's possible for them to share the same connection >> safely under FastCGI, since it is multi-process, just like mod_perl with >> the prefork MPM. The DBIx::Class code never shares connections across >> processes or threads. > > My impression was it was different, and that it does some kind > of management for that, but I could be wrong. I don't think anyone has actually solved the problem of sharing DBI handles across processes. It's the same as for mod_perl. >>From the man page: > > "It has auto-increment support for SQLite, MySQL, PostgreSQL, > Oracle, SQL Server and DB2 and is known to be used in production > on at least the first four, and is fork- and thread-safe out of > the box (although your DBD may not be)." In this case, "fork- and thread-safe" just means it opens a new connection if you try to use it after forking or spawning a thread. You can see this in the code. It's pretty simple. - Perrin Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Mason-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mason-users
