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.
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).
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||