|P is for Practical
bidirectional IPC (Linux)by Mirage (Sexton)
|on Nov 07, 2001 at 03:16 UTC
Mirage has asked for the wisdom of the Perl Monks concerning the following question:
I'm(still..)searching for a method of communicating between forked processes in both directions, I tried named pipes, pipes, Unix Domain Sockets but so far I have found nothing which is really useful in my case. I have a server which forks everytime a user connects, then the data the child gets from the client has to get back to the parent, but as every child does this, the connection has to be between one end and many ends, not as domain sockets are between one and one.
also i want to be able to read from it just for a short time, then do other things and read again. Or maybe someone can explain me how this 'often used' type of servers is done, with multiple clients which send and receive data from the server, at the same time as other clients of course, like a chat with tcp
(I dont want to do a chat nor do i want to use udp)
So my question is: Which method is to be preferred, and how would a chat server with tcp be done?
Thanks in advance.
2001-11-06 Edit by Corion : Removed superfluous blank lines
Edit: chipmunk 2001-11-06