Designing using fork() and TCP connection in C

Question

I have a question regarding on how to design the following system:

My system is built of several clients listening to an environment. When a audio threshold is breached they send their information to a server, that has children listening on each connection. The server needs information from all the clients to make the necessary calculations.

Currently the server is working in UNIX and has forked out connections. They are working independently.

What I want to do is to tell the parent (in the server) that information has been sent and it's now time to process it. How should I do it?

I'm thinking of possible different ways to do it:

Using signal()in Unix to somehow tell the parent that something has happened
Convert to Threads and use some wait and notify functions

The signaling is preferable but I cannot figure out how to do it efficiently. Because the following can happen in my system:

If all the clients successfully sent information to their children of the server, how can I tell the parent that I'm ready in a efficient way? Don't know/I'm uncertain of how it will process them.
The server may not receive information from all clients. So the parent must wait for awhile for all the children but not too long. So I'm guessing some sort of timer?

Are you sure you want to do this with tasks? It seems more like you want to use threads instead. Unfortunately your question is not that clear. — Dacav
– Dacav, Commented Jan 14, 2013 at 9:28
I'll add more information but the question is clearly stated — Mazze
– Mazze, Commented Jan 14, 2013 at 9:33
Please specify the operating system, solutions might differ depending on that. — vladmihaisima
– vladmihaisima, Commented Jan 14, 2013 at 9:47
@KillianDS I can see why this is a bit vague and I really hesitated to post this here cause I knew that some people would find it unrelated cause there is no direct problem. That's why I named it a design question. But read the whole question. The protocol is stated in the title. The communication is also stated in the question. One server, many clients. Server has children that handles each connection seperatly. The clients send information to the server. It's as simple as that. I'll add more text to explain some more of the system. — Mazze
– Mazze, Commented Jan 14, 2013 at 9:49
@vladmihaisima The operating system is described in the question already — Mazze
– Mazze, Commented Jan 14, 2013 at 9:51

Martijn Pieters · Accepted Answer · 2015-08-08 15:37:19Z

3

Doen't use fork, and don't use signals. Use a thread pool.

edited Aug 8, 2015 at 15:37

Martijn Pieters

1.1m326 gold badges4.2k silver badges3.4k bronze badges

answered Jan 14, 2013 at 9:52

Robert S. Barnes

40.9k32 gold badges136 silver badges182 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Mazze Over a year ago

Ah well, seems like I have to implement that. Thanks for convincing me

Davide Berra · Accepted Answer · 2013-01-14 10:02:32Z

2

What about a Unix Domain Socket for an inter-processes communication between children and father?

http://en.wikipedia.org/wiki/Unix_domain_socket

As soon as a child receives data through the TCP connection, the same data will be forwarded to the father process through the Unix Domain Socket and the latter process will be instantly notified

answered Jan 14, 2013 at 10:02

Davide Berra

6,6382 gold badges33 silver badges55 bronze badges

Collectives™ on Stack Overflow

Designing using fork() and TCP connection in C

2 Answers 2

1 Comment

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

1 Comment

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related