First let's break it down what it means to be federated,
pluggable and a message-exchange protocol. By federated
mean that Bester operates in a similar network topology to that of e-mail or XMPP whereby users registered on one
server can interact with those registered on another. By pluggable we are implying that Bester is a generalized protocol
that supports sub-protocols that can run on top of it to handle different message types and that these "handlers" are
separate processes communicated with via IPC. And last but not least, message-exchange, this is pretty obvious, it's
a network for exchanging messages, what these messages are is up to the developer writing a sub-protocol to run
on top of a Bester-based network.
Downloads available below (for the daemon).
||bester daemon, serves the protocol
||D library for interacting with bester
sending and receiving of messages