Open hatt opened 8 years ago
Hey there @hatt! Pusher could definitely be made optional, it was just the easier way to go when the project was originally ruby. I think it'd be reasonable to just replace Pusher with a pure websockets implementation.
That sounds like exactly what we need, thanks for the quick response. Is this already on the roadmap then? I'm comfortable enough with Go that I could probably hack on the server component but I know nothing about Javascript and how it negotiates the ws.
Tugboat ticks pretty much all the boxes at my company, only we don't really want to setup Pusher since we already have a bunch of internal websocket servers. Would it be a major change to make Pusher optional and default to plain old websockets?