go-events
go-events copied to clipboard
docker
Composable event distribution for Go
Useful, e.g. for metrics. This will allow the registry to use queue from this package, per docker/distribution#1553 and docker/distribution#2550. Signed-off-by: Elliot Pahl
Fixes #29 It uses the `default` case lower priority to check first if the `Channel` sink is closed.
I am new to this events project, want to understand whether docker swarm cluster support publisher / reader pattern. I am looking for way working like this: 1. there is...
If you have a `Queue` writing to a `Channel` and call close on the `Queue`, `Queue.Close` will block on writing to `Channel.Write`. This is because the `Close` waits on the...
The old `NewQueue` factory is left unchanged (infinite queue). A new `NewSizedQueue` factory is provided with an additional parameter, the size of the `Queue`. Writting when the queue is full...
When calling a `Channel` sink's `Write` method after having called its `Close` method, the select behaviour is non-deterministic, and may result in a valid `Write` call when it should return...
Add round-robin sink that will split the events among the destiny sinks evenly. If there is no sink `ErrNoSink` is returned. It is useful as an event load balancer. It...
Add error handling sinks that allow to react to further sinks errors by either droping the errors or closing the sink. They are useful to combine with other sinks such...
Add timeout sink that returns ErrSinkTimeout if the destiny sink does not return in the specified time. It is based on docker/swarmkit implementation but it does not close the sink...
Given that `go-events` is a library, it shouldn't log any information. If logging is considered essential, the choice of the logger should be left to code making use of the...
