In some situations, the user may not want the burden of having to keeping Subscription/Registration objects "alive". Topic and Procedure should provide a .permanently() option which indicates that the subscription/registration will be valid for the lifetime of the Session object. This option would also make the Session object keep its own copy of the Subscription/Registration shared objects.
If this option is used, the user has to ensure that the callbacks can be called while the Session is established.
In some situations, the user may not want the burden of having to keeping
Subscription
/Registration
objects "alive".Topic
andProcedure
should provide a.permanently()
option which indicates that the subscription/registration will be valid for the lifetime of theSession
object. This option would also make theSession
object keep its own copy of theSubscription
/Registration
shared objects.If this option is used, the user has to ensure that the callbacks can be called while the
Session
is established.