Opened 16 years ago
Last modified 14 years ago
#347 closed feature request
Message queue for communication between AppDomains and Threads — at Initial Version
Reported by: | kgrading | Owned by: | kgrading |
---|---|---|---|
Priority: | low | Milestone: | HeuristicLab 3.3.0 |
Component: | Hive.Client.Common | Version: | 3.2 |
Keywords: | Cc: |
Description
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 ID.
The ID is used for additional identification purposes (e.g. The message is something like GetFinishedJob and the ID would be the id of the execution engine, sending this request)
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.