Hey guys and gals! This is a project I'm undertaking to help myself learn Go - which I think is AWESOME so far. Any suggestions or criticisms would be appreciated. I hope to add more features as time goes on (and possibly swap out the generic WebSocket implementation with go-socketio).

I while ago I wrote something similar with a friend for fun. Redis, ServerSentEvents and Go: https://github.com/vivienschilis/eddy/

It's not so well documented but it's practically the same except that it uses ServerSentEvents on the client and has buffers so no message is ever dropped. Each messages contains the payload, a TTL and a channel size. The TTL is used to expire a channel automatically and the channel size can be used for example to create 1-deep channels for updating values like progress.

Shameless plug, but I also have a Go module named Goatee. However, it's a testing package: https://github.com/jprichardson/goatee-go It's too bad that discoverability of modules in Go sucks.

If you're only pushing data realtime to down the client and don't need realtime upload, then consider Server-Sent Events (http://www.w3.org/TR/eventsource/) as an option.

SSE is HTTP-compatible, so for example works on mobile networks that force port 80 to go through "transparent" WebSocket-disconnecting HTTP proxy.

Additionally you get Flash-free polyfills for IE7+ and automatic reconnection on error built into browsers.

What a coincidence, I see you use JSON config files: I wrote a tiny package to parse commented JSON files not long ago, maybe it would be a good fit for Goatee?

https://github.com/sauerbraten/jsonconf

Where's the license?

Why does this have zero tests?

That name almost made me not click on the link...