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

Improved dispatch (MTC) #635

Closed
RichardHightower opened this issue Mar 24, 2016 · 1 comment
Closed

Improved dispatch (MTC) #635

RichardHightower opened this issue Mar 24, 2016 · 1 comment

Comments

@RichardHightower
Copy link
Member

Our dispatch is setup so we can create proxies to local serviceQueues and expose them via REST/Websocket.

The problem is we only handle dispatch from local service queue and REST/Websocket IO, if we wanted to expose a service to another IO channel like Kafka or VertxEventBus, etc. there is no easy way to do it.

I propose the following change.

MethodCall should have a Callback associated with it.
If this Callback is set, this is the integration point for REST/WebSocket/VertxEventBus/ etc.
Instead of using the more hacky way of direct reponsequeue access now.

We may want to make responsequeue and internal concept as well.

@RichardHightower
Copy link
Member Author

This was easier than imagined.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant