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.

Sign up for GitHub

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

Jump to bottom

Support for message headers being transferred from senders to receivers #11

Closed
gsteinacker opened this issue May 15, 2018 · 0 comments
Closed

Support for message headers being transferred from senders to receivers #11

gsteinacker opened this issue May 15, 2018 · 0 comments
Assignees
@gsteinacker
Labels
enhancement

Comments

@gsteinacker
Copy link
Member

gsteinacker commented May 15, 2018 •
edited

headers should not only be used to provide access to SQS and Kinesis meta-data. Instead, it should be possible to use them in a similar way as in HTTP requests headers.

See Epic #37
@gsteinacker gsteinacker added this to the 1.0.0 milestone May 15, 2018
@gsteinacker gsteinacker self-assigned this May 15, 2018
@gsteinacker gsteinacker removed their assignment Sep 21, 2018
@gsteinacker gsteinacker mentioned this issue Oct 25, 2018
Closed
@gsteinacker gsteinacker modified the milestones: 1.0.0, 1.0.0-m1, 1.0.0-m2 Oct 25, 2018
@gsteinacker gsteinacker mentioned this issue Oct 25, 2018
Open
@gsteinacker gsteinacker removed the to do label Oct 25, 2018
@gsteinacker gsteinacker modified the milestones: 1.0.0-m2, 1.0.0-m1 Nov 19, 2018
@gsteinacker gsteinacker self-assigned this Nov 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gsteinacker gsteinacker

Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gsteinacker