Consider adding a Service class which serves as a facade to a common Session instance. Multiple Service objects could target the same Session instance. A Service would take care of maintaining lists of scoped registrations/subscriptions specific to that service. When a Service is destroyed, it would automatically clean up its own RPC registrations and pub/sub subscriptions without affecting other running services. A Service could have its own URI prefix that is automatically prepended to registration/publication URIs.
Something like this has already been implemented in the closed-source parent project that uses this library.
Consider adding a
Serviceclass which serves as a facade to a commonSessioninstance. MultipleServiceobjects could target the sameSessioninstance. AServicewould take care of maintaining lists of scoped registrations/subscriptions specific to that service. When aServiceis destroyed, it would automatically clean up its own RPC registrations and pub/sub subscriptions without affecting other running services. AServicecould have its own URI prefix that is automatically prepended to registration/publication URIs.Something like this has already been implemented in the closed-source parent project that uses this library.