Hi Dominique,
currently, WAMP only specifies "shared registrations", that is call
dispatching along one of the following policies:
'single'
'roundrobin'
'random'
'first'
'last'
it would be straight forward to translate this to "shared
subscriptions", where the first subscriber via SubscibeOptions makes the
subscription a shared one, and all subsequent subscribers will
automatically share the former, first subscription.
the broker would dispatch events no longer to all subscribers, but only
one of them based on the respective policy.
this would fit into the existing design, moreso: in a way, it would be a
strange asymmetry _not_ have this option in pubsub, but only in rpc.
Would above work for what you wanna do?
If so, the following would be needed to make it happen in WAMP:
1. issue on the WAMP repo for the feature
2. PR on the WAMP repo for spec text
3. issues on AutobahnPython and Crossbar.io repos
4. implementation PR for AutobahnPython
5. implementation PR for Crossbar.io
The time to get this merged: I'm +1, and I guess we should have it
sooner or later .. but we as a company/project don't have time right now
.. so timeline depends on community contributions ..
Cheers,
/Tobias