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 Dec 27, 2022. It is now read-only.
Is your feature request related to a problem? Please describe.
It might be worth considering to allow multiple clients subscribing for the same public identifier, but with different URLs. One way that could be done is by adding a client-provided subscriber ID that must be unique; or by hashing the evts data to get a unique ID for every client.
This would allow multiple RestServerNodeService classes to connect to the same server-node instance with a high degree of control over the events
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is your feature request related to a problem? Please describe.
It might be worth considering to allow multiple clients subscribing for the same public identifier, but with different URLs. One way that could be done is by adding a client-provided subscriber ID that must be unique; or by hashing the evts data to get a unique ID for every client.
This would allow multiple
RestServerNodeService
classes to connect to the sameserver-node
instance with a high degree of control over the eventsThe text was updated successfully, but these errors were encountered: