Opened at 2009-05-24T16:33:19Z
Closed at 2026-09-26T01:38:26Z
#107 closed planned (wontfix)
investigate explicit locking of MObjectRef
| Reported by: | Ichthyostega | Owned by: | Ichthyostega |
|---|---|---|---|
| Priority: | lesser | Milestone: | 2beta |
| Component: | lumieraSteam | Keywords: | obsolete |
| Sub Tickets: | Parent Tickets: | #1435 |
Description
Investigate the question if we need an explicit locking mechanism on external references to MObjects. Currently I don't think so, but this question can't be decided without a much more complete implementation of the object handling and the build/render process.
The problem is due not so much to the MObjects themselves (which are kept alive by the refcount), but to the placements, which theoretically could be modified in parallel...
Change history (1)
comment:1 by , at 2026-09-26T01:38:26Z
| Keywords: | obsolete added |
|---|---|
| Parent Tickets: | → 1435 |
| Resolution: | → wontfix |
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
MObjectRefis a design approach that was entirely obsoleted through the gradual shift in the Lumiera architecture. The primary focus is now placed on de-coupling and symbolic representation. Actions will be entered through an Event-Log, and the model data structure is now understood as a projection (⟶ Event-Sourcing, CQRS)marked as tag:obsolete