Only general purpose notifications are supported?
PavelPolyakov opened this issue · comments
Am I understand right, that currently it's only possible setup the server for the general notifications.
For example, my goatee works on 1234 port and subscribed to the Redis channel "A", and the client is listening to this host and port.
I have 2 customers, C1 and C2. I want to send the notification to C1 and to C2, the different notifications. Currently it's not possible to do that, right? It could only be managed through the conditioning on the client side, which is not safe.
Yep, absolutely correct. I'm working on adding the ability to subscribe to multiple channels and define what routes you'd like those channels on.
Multiple-channel Redis subscriptions are now supported. Client differentiation is incoming.
Hi John,
Wanted to ask you one more time.
I'm working on adding the ability to subscribe to multiple channels and define what routes you'd like those channels on.
As I see you've added the support of multiple channels, but nothing about the custom routes.
My main question is - how can we, using goatee, implement the next concept - each customer have it's own connection with the server, and he is notified about the new private messages (for example) via those websockets. And the other customers are not able to simply connect to the same socket and read the content.
Can you explain me if it's possible to do with goatee and how? I'm curios about the concept despite the WS library.
Thanks in advance, for any advice about this.