Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Are there any situations when it worth to use realtime signals for interprocess communication(or any other reason actually)?
For me it seems like all the difficulties with them make the code overcomplicated, difficult to maintain and potentially full of bugs.
It would be nice if somebody could show that I’m mistaken.
Thanks,
Alex.
Notably, realtime signals are used internally in the NPTL implementation of pthreads.
Realtime signals, unlike their basic counterparts, will queue, making them useful for edge-triggered IO readiness indication.
Realtime signals, unlike their basic counterparts, can also carry an
int/pointer’s worth of arbitrary data. I can think of several times I’ve wanted to send just a bit more data along with a notification.I’m not sure what you mean by “overcomplicated, difficult to maintain and potentially full of bugs.”