Default signal handler observers should have the option of indicating other mechanisms for notification (e.g. MutexSemaphore, callback, SubjectEvent post).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There is a per-thread interaction relationship that should be explored. In other words, since most signals are/can be thread configurable should the management of signals become part of Thread?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Provide a mechanism that enfolds kernel or process signal handling. Possible core classes, certainly a framework opportunity.
NOT TO BE CONFUSED WITH Subject<--->Observer pattern.
There should be a default handler mechanism for signals.
The default signals should be optionally replaced.
The default signal handlers should allow observers.
Default signal handler observers should have the option of indicating other mechanisms for notification (e.g. MutexSemaphore, callback, SubjectEvent post).
Synchronous and Asynchronous signals should be supported.
Support for Signal masking and handling by multiple threads of execution.
There is a per-thread interaction relationship that should be explored. In other words, since most signals are/can be thread configurable should the management of signals become part of Thread?
A Signal can identify it's handler method.