Ticket #133 (closed defect: fixed)
Synchronize access to COBIA objects from COM
Reported by: | jasper | Owned by: | jasper |
---|---|---|---|
Priority: | major | Milestone: | Maintenance of Phase II |
Component: | COMBIA | Version: | 1.2.0.10 |
Keywords: | Cc: |
Description
COMBIA registers DEFAULT threaded COBIA objects as Both, which implies the COM side may be instantiated as MTA, which in turn implies multiple concurrent incoming calls are in theory possible. COMBIA should shield against this.
This should be one synchronization object (e.g. std::mutex) per PMC objects - including all its primary PMC objects to agree with DEFAULT threading model.
Change History
comment:2 Changed 2 years ago by jasper
My issue is that currently COMBIA advertises COBIA PMCs as Both (in Phase II). That is why it would be reasonable to fix it now.
comment:3 Changed 2 years ago by jasper
- Status changed from new to closed
- Resolution set to fixed
In [302]:
comment:10 Changed 2 years ago by jasper
Note: See
TracTickets for help on using
tickets.
Is this really within the milestone Maintenance of Phase II? Resolution of this waits for COBIA Threading Models to be formally approved while M&T SIG is still working on the document describing these, and a RFC phase will take place once M&T SIG has completed the document. The design of COBIA Threading Models is a task in parallel to COBIA Phase III. So should the milestone for this ticket be Phase III or when the WP1 Phase III branch will be merged with Phase II trunk?