This is a nifty thought, but I'd worry that it would make the
parent/server a bit monstrous and hard to get right. I guess
if each child request is read, executed and answered back to
the child in one block, it's certainly manageable.
in reply to Re: Sharing database handle
in thread Sharing database handle
There still is the empirical question: is it better to
serialize all activity through a single, very active connection, as
opposed to having a bunch of connections (leaving it to the
DBMS to coordinate the actions, which is, in part, what
it was written to do)? I don't really know that yet (sorry).