Multiple channels on the server could easily be supported, just need a scheme for getting the messages out.
A new interface, such as this HTTP schema
GET /:channel/all
GET /:channel/recent/:n
GET /:channel/between/:start/:end
PUT /:channel/clear
PATCH /:channel/:id
would allow for modification and other things that it could do, but doesn't because of the limited read-only streaming nature
a simple TCP interface could be built with a similar scheme, but with a json types, to keep the client requirements simple.
Multiple channels on the server could easily be supported, just need a scheme for getting the messages out.
A new interface, such as this HTTP schema
a simple TCP interface could be built with a similar scheme, but with a json types, to keep the client requirements simple.