#347 closed feature request (done)
Message queue for communication between AppDomains and Threads
| Reported by: | kgrading | Owned by: | kgrading |
|---|---|---|---|
| Priority: | low | Milestone: | HeuristicLab 3.3.0 |
| Component: | Hive.Client.Common | Version: | 3.2 |
| Keywords: | Cc: |
Description (last modified by kgrading)
The message queue should be implemented as a List, containing MessageContainer Objects. A MessageContainer Object consists of 2 Parts: The actual Message (will be implemented as a Enumerator called MessageType) and an additional JobId.
The JobId is used for additional identification purposes (e.g. The message is something like GetFinishedJob and the ID would be the the job, that has finished. This required tracking which job runs in which Execution Engine.)
The list should use a synchronization mechanism (e.g. a semaphore) that blocks the core thread, when no more messages are available for processing. Additional locking should not be necessary due to the fact, that there is only one consumer.
Change History (6)
comment:1 Changed 16 years ago by kgrading
- Status changed from new to assigned
comment:2 Changed 16 years ago by kgrading
- Description modified (diff)
- Priority changed from major to minor
comment:3 Changed 16 years ago by kgrading
- Resolution set to fixed
- Status changed from assigned to closed
comment:4 Changed 16 years ago by swagner
- Milestone changed from Hive 1.0 to Iteration 0
Milestone Hive 1.0 deleted
comment:5 Changed 14 years ago by swagner
- Milestone changed from Iteration 0 to Current
Milestone Iteration 0 deleted
comment:11 Changed 14 years ago by swagner
- Milestone changed from Current to HeuristicLab 3.3.0
Milestone Current deleted
implemented the queue in r734