⚠️ indicates a breaking change.
[Unreleased]
Added
Changed
Removed
[0.4.0] - 2024-09-10
Changed
- ⚠️ Updated to
ump-ngto0.2.0.
[0.3.0] - 2024-02-20
Yanked 0.2.1 and rereleased as 0.3.0 due to breaking changes.
[0.2.1] - 2024-02-20
Added
- Add a watchdog that will warn if a msgproc takes more than 200ms to return.
This is intended for dev builds only and must be enabled using the
watchdogfeature. Will output to stderr by default, but will output totracing::warn!()if thetracingfeature is enabled as well.
Changed
- Make
Handlerbuilder closure fallible.
[0.2.0] - 2024-01-28
Changed
- Instead of taking in an
impl Handlerinto the{thread,task}::spawn()function, take in a closure that returns the handler. A reference to the handler channel's client endpoint is passed to the closure, which makes it possible to storeClient/WeakClientin the handler, without involving anOption(or similar).
Removed
- Removed the
{thread,task}::spawn_preinit()functions. These no longer really serve a purpose since the deferred handler construction was introduced.
[0.1.2] - 2024-01-21
Added
- There are new spawn thread/task functions (with the suffix
_preinit) that take in a ump-ngServerand assumes that the message handler has already been initialized. This is useful if the handler itself needs contain a (weak) client reference, and one does not wish to store it in anOption.
[0.1.1] - 2024-01-14
Changed
- Re-export
ump-ng.
[0.1.0] - 2023-10-03
Initial release.