Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Optimize EVENT and INVOCATION for exact matching Subscriptions/Registrations #29

oberstet opened this issue Dec 24, 2013 · 2 comments


None yet
1 participant
Copy link

commented Dec 24, 2013

In case a Subscription or Registration is using "match" == "exact", there is no need to forward the PUBLISH.Topic or CALL.Procedure again within EVENT.Topic or INVOCATION.Procedure.

In this case, the Broker or Dealer SHOULD transmit "" (the empty string) for the respective message elements.


This comment has been minimized.

Copy link
Member Author

commented Dec 27, 2013

There is a downside to this: Subscriber implementations would need to store the subscribed topic if they want to maintain a uniform API to application code: onEvent(topic, event).

With Topic always being filled in the EVENT message, Subscribers can get away with a simple Subscription|id => Event Handler map.


This comment has been minimized.

Copy link
Member Author

commented Jan 3, 2014

We can solve this differently: move the message fields EVENT.Topic and INVOCATION.Procedure to EVENT.Details.topic and INVOCATION.Details.procedure and make those mandatory if pattern-based subscription or registration is in place.

@oberstet oberstet closed this in 1b4fd4e Jan 3, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.