Enhancement #548
Updated by J. Moringen over 12 years ago
For performance (and other) reasons, it can be handy to avoid reduce overhead of multi-threading. Therefore, a threadless RSB configuration should be possible. Actually, the result should be that a simple in-process variant of RSB uses exactly one thread. is planned.
For this, a number of issues have to be solved:
* DirectEventSendingStrategy ✓
(Done)
* DirectEventReceivingStrategy ✓, r2522
(Uses (use the caller's callers thread context to dispatch events)
* Factory for Sending and Receiving strategies ✓ for receiving, r2531
* Integration plus integration in config mechanism ✓ for receiving, r2533
(actually, the result should be that a simple in-process variant of RSB uses exactly one thread)
* For the SpreadConnector the Reader pattern needs to be implemented to stick with the single thread
For this, a number of issues have to be solved:
* DirectEventSendingStrategy ✓
(Done)
* DirectEventReceivingStrategy ✓, r2522
(Uses (use the caller's callers thread context to dispatch events)
* Factory for Sending and Receiving strategies ✓ for receiving, r2531
* Integration plus integration in config mechanism ✓ for receiving, r2533
(actually, the result should be that a simple in-process variant of RSB uses exactly one thread)
* For the SpreadConnector the Reader pattern needs to be implemented to stick with the single thread