Tell Wave to use Redis explicitly, to avoid clash with default broadcast connection being Pusher?

[dlebech]

Hi, thanks for a great project.

The setup

• I have a Laravel project using Pusher for websockets, so we have BROADCAST_CONNECTION set to pusher in our config, which in turn is then the "default" broadcast driver.
• I get the initial connection event (general.connected) when connecting to wave
• For custom SSE-specific events, I can set $this->broadcastVia('redis'), and then it will actually work fine for public channel broadcasts.

The problem

However there are two problems with the above setup:

1. The default "general.ping" event is never delivered -- probably because it just uses the default broadcast connection (which is set to pusher)
2. Private channels don't work, and looking at the code, I can see Wave uses the static Broadcast::auth(..) function, which is then implicitly using the pusher broadcaster -- and I get some generic error about a socket id being null.

The question

Is there a way to make this work in a better way, by somehow explicitly telling wave to use the redis broadcast connection for everything (perhaps via some config), or are we out of luck for this scenario?

Two extra notes:

• Yes, I can confirm that changing the default (i.e. BROADCAST_CONNECTION) to redis makes everything work, including private channels
• Other solutions I haven't tried yet is to reverse our setup so redis is the default and pusher is used for specific events -- but it's a larger operation for us to change that right now.