faustinoaq changed the topic of #amber to: Welcome to Amber Framework community! | https://amberframework.org | Developer happiness, productivity and bare metal performance | GH: https://github.com/amberframework | Docs: https://docs.amberframework.org | Gitter: https://gitter.im/amberframework/amber | IRC Logger: https://irclog.whitequark.org/amber | Amber::Server.start
<FromGitter> <damianham> Let's say that I have this javascript code in a React SPA ⏎ ⏎ ```Sockets::Signal.send_signal("xyz", "update", data)``` ⏎ ⏎ that emits the 'data' to connected clients in channel 'xyz'. The way I am reading it, clients connected to the socket on process A will not get the data received in process B. Is that correct or is there interprocess communication so that when process B emits data on a socket channel
<FromGitter> ... it is emitted to the same channel in all running processes of the application ? [https://gitter.im/amberframework/amber?at=5e84593ac6ac331cf3eb6965]
<FromGitter> <drujensen> That is correct. We never implemented a redis shared memory solution for the websockets. You wouldn’t be able to spin up multiple boxes behind a load balancer either.
<FromGitter> <drujensen> Something we will need to make the websocket solution viable IMO.
Guest66303 has left #amber [#amber]
t1|Mike_ has joined #amber
t1|Mike has quit [*.net *.split]
t1|Mike_ is now known as t1|Mike
t1|Mike has quit [Changing host]
t1|Mike has joined #amber