micahparks / websocket-pubsub

An in-memory HTTP websocket publish-subscribe system written in Golang.

Find me on the internet

My personal website: link

• This has a contact form, if you'd like to report a security sensitive bug or send a kind message.

StackOverflow: link

If you appreciate my work, consider supporting me via a one-time or monthly financial contribution via GitHub Sponsors.

websocket-pubsub's Issues

Allow servers to proxy

Proxy pubsub servers should be implemented.

A central pubsub server could be at site A and a user's proxy pubsub server could be at site B. This would allow multiple subscribers at site B to get the same subscriber information with multiple connections to the proxy pubsub server at site B, but only one connection to the central pubsub server at site A.

Considerations:

• One proxy server may make multiple connections to the central pubsub server. One per subscription topic. If this can be reduced to one connection, that would be best, but a control channel may be required for that, which is undesired.

Add test for ping ticker

The publisher and subscriber should ping on the specified interval. Make a Go test to cover that.

Create a JavaScript client

A client can be implemented in any language, but the next implementation of the client should be written in JavaScript for use in web browsers.

Remove variadic arguments where possible

Some functions, like New functions, have a variadic argument for options. Make these options mandatory and singular, for simplicity.