Thread Safety #36

Open
opened 2022-01-15 22:26:30 +01:00 by kske · 1 comment
Owner

EventBus should be mostly thread safe already, but that should be verified and ideally tested.

`EventBus` should be mostly thread safe already, but that should be verified and ideally tested.
kske added the
enhancement
core
should have
21
labels 2022-01-15 22:26:30 +01:00
kske self-assigned this 2022-01-15 22:26:30 +01:00
Author
Owner

As it turns out, EventBus isn't actually thread-safe in the context of registering listeners and dispatching events. The underlying collections are, but that's not sufficient when the aforementioned high-level operations are executed simultaneously on multiple threads.

I am working on an efficient and complete thread-safety implementation based on StampLock.

As it turns out, `EventBus` isn't actually thread-safe in the context of registering listeners and dispatching events. The underlying collections are, but that's not sufficient when the aforementioned high-level operations are executed simultaneously on multiple threads. I am working on an efficient and complete thread-safety implementation based on `StampLock`.
kske added the
bug
label 2022-01-18 21:56:46 +01:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: zdm/event-bus#36
No description provided.