You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The original idea in this case is that a separate read and write handle could be given depending on what a process needs.
In this case, one to ACK a signal from the read side and write side would be necessary: the reader case should be obvious, but in the writer case, it may wish to abort any signals not yet received.
The more this is looked at, the more this seems like it's really just bad API design, and only the reader should be able to terminate a signal.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The original idea in this case is that a separate read and write handle could be given depending on what a process needs.
In this case, one to ACK a signal from the read side and write side would be necessary: the reader case should be obvious, but in the writer case, it may wish to abort any signals not yet received.
The more this is looked at, the more this seems like it's really just bad API design, and only the reader should be able to terminate a signal.
Beta Was this translation helpful? Give feedback.
All reactions