otto/eventbus
R Tyler Croy 22d273aa97
Add the default channels as described in RFC 0003
2019-12-30 07:30:06 -08:00
..
src Add the default channels as described in RFC 0003 2019-12-30 07:30:06 -08:00
static Add the default channels as described in RFC 0003 2019-12-30 07:30:06 -08:00
templates Start passing around messages internally which can be serialized to JSON 2019-12-27 12:54:44 -08:00
.gitignore Incorporate the newer actix-web components which use async/await 2019-12-27 11:26:40 -08:00
Cargo.toml Add some simplistic configuration via eventbus.yml 2019-12-27 14:33:22 -08:00
README.adoc Add some simplistic configuration via eventbus.yml 2019-12-27 14:33:22 -08:00

README.adoc

<html lang="en"> <head> </head>

Otto Eventbus

The Otto eventbus is intended to provide an API shim which can be easily ported to a number of backend durable queueing and eventing systems. The default implementation simply uses an in-memory queue for simplicitys sake, and has no durability guarantees.

Clients are expected to register for events which will come over a single WebSocket channel.

</html>