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

Reactive HTTP and WebSocket connector enhancements #13466

Closed
6 tasks
michalszynkiewicz opened this issue Nov 25, 2020 · 3 comments
Closed
6 tasks

Reactive HTTP and WebSocket connector enhancements #13466

michalszynkiewicz opened this issue Nov 25, 2020 · 3 comments
Assignees
@michalszynkiewicz
Labels
area/reactive-messaging kind/enhancement New feature or request

Comments

@michalszynkiewicz
Copy link
Member

michalszynkiewicz commented Nov 25, 2020 •
edited
Loading

  • add support for STOMP or some other protocol that allows acking/nacking by the remote websocket endpoint
  • support text messages for websockets
  • add content type headers in http serializers
  • websocket source exception mapper
  • improve conversion error reporting (ATM we have 500 instead of 422 in such case)
  • give a possibility to read response for sent out messages
@michalszynkiewicz michalszynkiewicz added the kind/enhancement New feature or request label Nov 25, 2020
@ghost ghost added the triage/needs-triage label Nov 25, 2020
@michalszynkiewicz michalszynkiewicz self-assigned this Nov 25, 2020
@cescoffier
Copy link
Member

@michalszynkiewicz is this issue still relevant?

@michalszynkiewicz
Copy link
Member Author

I still think these enchancements make sense.
I don't know when we'd be able to implement them though.

@michalszynkiewicz
Copy link
Member Author

moved to quarkiverse/quarkus-reactive-messaging-http#58

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@michalszynkiewicz michalszynkiewicz

Labels
area/reactive-messaging kind/enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cescoffier @michalszynkiewicz