Free cookie consent management tool by TermsFeed Policy Generator

Changes between Initial Version and Version 2 of Ticket #347


Ignore:
Timestamp:
11/11/08 15:05:24 (15 years ago)
Author:
kgrading
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #347

    • Property Status changed from new to assigned
    • Property Priority changed from major to minor

  • Ticket #347 – Description

    initial v2  
    11The message queue should be implemented as a List, containing MessageContainer Objects.
    22A MessageContainer Object consists of 2 Parts:
    3 The actual Message (will be implemented as a Enumerator called MessageType) and an additional ID.
     3The actual Message (will be implemented as a Enumerator called MessageType) and an additional JobId.
    44
    5 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)
     5The 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.)
    66
    77The 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.