Couple of responses:
- I was under the impression that every network socket has an associated domain socket (not that I ever checked).
- You said you had already tried UDS
- Exactly how many processes were you planning to use? There are 64000 possible sockets which means that you can have 32000 forked processes before you run out of sockets.
- If you are trying to write code for a machine that can handle 32000 processes, grab the Apache source code since that is the canonical example of a really good forking server. And then give me an account on your machine :)
- If you read the pod, my goal was portable reliable forking IPC.
- 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.
- 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.
____________________
Jeremy
I didn't believe in evil until I dated it.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
