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
A class to handle firing events that are received by a registered handler on another machine would be incredibly useful.
This will likely need to be broken down into multiple pieces to work on. There needs to either be a central server to route the events to the handlers or some kind of common configuration so the firing instances can connect to all the handlers and deliver the messages in a more peer too peer style.
A central server is likely easier to implement and easier to set up (only need a single url/ip in a config somewhere), built potentially harder to scale.
The text was updated successfully, but these errors were encountered:
A class to handle firing events that are received by a registered handler on another machine would be incredibly useful.
This will likely need to be broken down into multiple pieces to work on. There needs to either be a central server to route the events to the handlers or some kind of common configuration so the firing instances can connect to all the handlers and deliver the messages in a more peer too peer style.
A central server is likely easier to implement and easier to set up (only need a single url/ip in a config somewhere), built potentially harder to scale.
The text was updated successfully, but these errors were encountered: