Joël Gähwiler
Joël Gähwiler
Closing as stale, please reopen if issue persists.
Closing as probably solved.
As @biteater pointed out, the only reason for the `onMessage` callback to be called is because of a subscription to a topic. And if you publish to the same topic...
We should expose `lwmqtt_drop_overflow` to skip too large messages.
Added in eae214b1c2ca0d861037617a0ed0128e3c5ec306.
Closing as stale, please reopen if issue persists.
Closing as stale. Please reopen if issue persists.
Closing in favour of #294.
I managed to implement a rough sketch of the feature with very few changes to the server and client library: - https://github.com/256dpi/nats-streaming-server/compare/master...256dpi:ssf - https://github.com/256dpi/go-nats-streaming/compare/master...256dpi:ssf As I'm new to the internals...
Fixed in ebf53c0. Will be available in next release.