>You said you had already tried UDS
i dont think that either uds or sockets are good for that, but ok that may be wrong
>I am currently reworking the architecture so that you can drop in any transport layer that you want to
>use - I have a demo using SysV message queues, and I can't wait to hear your comments on that one.
cool
>The basic architecture of my code is useful for a preforking server, regardless of the transport layer.
>For someone who doesn't even know what select does,
>you seem to be pretty good at pointing out why code you don't understand is unsuitable for your purpose.
sorry about that, but i read the pod, and thats what i
took as source for my opinion, but nevertheless i will try your module, and maybe then, if i ever get it running with pipes, will compare the speed and reliability of both.
But sure, your way is an easy one.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
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:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.