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

Migrate Message Sequence #164

Closed
pardahlman opened this issue Dec 4, 2016 · 0 comments
Closed

Migrate Message Sequence #164

pardahlman opened this issue Dec 4, 2016 · 0 comments
Assignees
Labels
Milestone

Comments

@pardahlman
Copy link
Owner

pardahlman commented Dec 4, 2016

In 2.0, Message Sequence is a State Machine. The signature will slightly change, as the IBusClient no longer is hard coupled to a Message Context.

@pardahlman pardahlman added the 2.0 label Dec 4, 2016
@pardahlman pardahlman added this to the 2.0.0 milestone Dec 4, 2016
@pardahlman pardahlman self-assigned this Dec 4, 2016
pardahlman added a commit that referenced this issue Feb 18, 2017
It is not enough that to use MessageRecived, it needs to
be Deserialized as well
pardahlman added a commit that referenced this issue Feb 19, 2017
This is done beause the recieiving part should be responsible
for deciding type. If all messages comes in on the same queue,
we need to use the type prop from the header, which creates a
dependency to type specified in producer.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant