You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 23, 2019. It is now read-only.
I'm trying to wrap my head around with the design of this example. One thing that is confusing me is the hubSource in UserActor. Why is it required that there is a fan-out mechanism here? I understand that sending stuff to the hubSink will propogate to the client via the websocketFlow, but I'm not sure what the requirement for the multiple consumers of the flow. Isn't UserActor created for each WebSocket connection via the UserParentActor? If so, who are the extra subscribers if they are not the users?
Thank you
The text was updated successfully, but these errors were encountered:
Hi,
I'm trying to wrap my head around with the design of this example. One thing that is confusing me is the
hubSource
inUserActor
. Why is it required that there is a fan-out mechanism here? I understand that sending stuff to thehubSink
will propogate to the client via thewebsocketFlow
, but I'm not sure what the requirement for the multiple consumers of the flow. Isn'tUserActor
created for each WebSocket connection via theUserParentActor
? If so, who are the extra subscribers if they are not the users?Thank you
The text was updated successfully, but these errors were encountered: