Enhancement #204
Remove DispatchTask on the way to OrderedQueueDispatcherPool
Status: | Resolved | Start date: | 02/22/2011 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | J. Wienke | % Done: | 100% | |
Category: | Python | Estimated time: | 2.00 hours | |
Target version: | - |
Description
Just on thread of indirection more than required.
Associated revisions
removed QueueAnddispatchTask to abvoid useless threading.
refs #204
remove QueueAnddispatchTask
refs #204
History
#1 Updated by I. Lütkebohle about 13 years ago
I don't understand the description ;-)
#2 Updated by J. Wienke about 13 years ago
Currently the SpreadReceiverTask reads messages from the line and decodes them, passes them to the DispatchTask, which in turn puts them in yet another queue in OrderedQueueDispatcherPool. The DispatcherTask can be completely removed. This is just yet another queue. ;) Instead SpreadReceiverTask can simply pass things to the OrdereQueueDispatcherPool.
#3 Updated by S. Wrede about 13 years ago
Basically, this is a regression in the design of the event dispatching code. Prior to the OrderedQueueDispatcherPool there was only a boost.threadpool instantiated, which lacked any sort of queuing. OrderedQueueDispatcherPool now includes both, threadpool and queuing.
BTW: The same should still apply to the C++ implementation.
#4 Updated by J. Wienke about 13 years ago
- Status changed from New to In Progress
- Estimated time set to 2.00
#5 Updated by J. Wienke about 13 years ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100