Alan Conway wrote:
Gordon Sim wrote:
There is also a subtle impact on some of the 'utility' classes that
can be used on top of the Session API. Previously the synchronicity of
interactions from these classes would be controlled by the mode on the
session, now the behaviour is defined as part of the classes themselves.
E.g. each SubscriptionManager::subscribe() is always synchronous now,
and each message-accept sent by the dispatcher in auto-acking mode is
always asynchronous.
Agreed - I think this is an improvement as otherwise we have to document
and test both options for every class.
Agreed. The current options are certainly the most obvious ones. If a
need arises to allow e.g. asynchronous subscription through the
subscription manager we can always add those capabilities based on that
demand.
