Tue, Jun 26, 2012 at 8:26 PM, Michael Schwartz <[email protected]> wrote:
> "You can also encounter this error with applications that fork child > processes, all of which try to use the same connection to the MySQL server. > This can be avoided by using a separate connection for each child process." > > Plus, I'd think that socket would become a significant bottleneck, since > you'd be talking basically to a single thread in the MySQL server... > That's the crux of my problem: i write almost exclusively library-level code and i can't enforce this type of policy on downstream clients in any useful way. So my only defense against such things is either not providing such a feature (let the client do it) or documenting them with "big fat hairy warning" labels :/. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
