thanks, I will look it up later and reply or msg if I have
problems(hopefully this is what I was looking for) | [reply] [Watch: Dir/Any] |
After looking at your module i think its of no real use
for me, nor for any other real server application, or
forking application, because having one one port for each process is too much, and why don't you use unix-domain-sockets? | [reply] [Watch: Dir/Any] |
| [reply] [Watch: Dir/Any] |
>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.
| [reply] [Watch: Dir/Any] |