Opened 15 years ago

#222 new defect

Optimized collective updates require frozen objects

Reported by: hauma Owned by: hauma
Priority: normal Milestone: 2.0
Component: uka.karo Version: 1.09b
Severity: normal Keywords:


The replicated root object is present at each rank of a replicated object. Since this could have been modified during a collective update, the underlying communication is always potentially all-to-all. To optimize collective updates effectively according to ticket:213, there must be the possibility to "freeze" at some point in time after construction. A frozen object must no longer be modified and is excluded from updates.

Attachments (0)

Change History (0)

Add Comment

Modify Ticket

Change Properties
Set your email in Preferences
as new The owner will remain hauma.
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from hauma to the specified user. Next status will be 'new'.
The owner will be changed from hauma to anonymous. Next status will be 'assigned'.

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.