Is there anything fundamentally preventing a message_bus ActionCable adapter?

[seanpdoyle]

I want to preface this issue by thanking you for your work on this gem (🎉), and emphasizing that this isn't a feature request.

Are there any fundamental conflicts that would prevent some inter-operability work to be done in support of an ActionCable adapter?

From the front-end side, it looks like an ActionCable.Consumer accepts an arbitrary URL (ws:// or https://).

On the back-end side, there are already several adapters, including adapters using Postgres and Redis.

I've only recently started working with the message_bus gem (so please correct me if I'm wrong), but as I understand it, the ActionCable::SubscriptionAdapter::Base API (i.e. broadcast, subscribe, unsubscribe) seems similar enough to the MessageBus API (i.e. publish, subscribe, unsubscribe) that some glue-code could be written to make the two compatible.

[SamSaffron]

Are there any fundamental conflicts that would prevent some inter-operability work to be done in support of an ActionCable adapter?

The only fundamental issue I can think about is that message bus is inherently reliable and action cable is best effort.

I am not sure how interoprability really would look, but I guess you could pull something off. The underlying paradigm mismatch though is not easy to solve.