Current design requires that the WS connection be on the same server as the hook call. If scaled to multiple instances it is possible that the hook cal will be received on a server which doesn't contain the WS connection.
Possible Solution: Use Wisper to have the hook endpoint publish the call, while all WS connections subscribe to that ID. This adds a dependency on Redis.
Current design requires that the WS connection be on the same server as the hook call. If scaled to multiple instances it is possible that the hook cal will be received on a server which doesn't contain the WS connection.
Possible Solution: Use Wisper to have the hook endpoint publish the call, while all WS connections subscribe to that ID. This adds a dependency on Redis.