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

HTTP Authorization Refactor #4979

Closed

Conversation

stuartwdouglas
Copy link
Member

This is a subset of #4956 that does not need the new quarkus-http release. If the other artifact is not published in time then ideally this one will go in as it fixes some problems (such as blocking ops on the IO thread)

@sberyozkin
Copy link
Member

@stuartwdouglas It all looks good, I'd only consider making it obvious that context is meant for the blocking calls (or even move it out of the signature if it is easy enough to do), as per this comment, unless you plan to add more operations to AuthorizationRequestContext, for the users be able to do more than just the blocking checks on this context instance.
What do you think ?

@stuartwdouglas
Copy link
Member Author

Eventually it may contain more context info, so I would rather leave it to future proof.

@sberyozkin
Copy link
Member

@stuartwdouglas OK, that makes sense. So may be it is worth pushing the doc about the blocking calls from the class itself to the method which does the blocking call ?

@sberyozkin sberyozkin self-requested a review October 29, 2019 11:42
Copy link
Member

@sberyozkin sberyozkin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@gsmet
Copy link
Member

gsmet commented Oct 29, 2019

Quarkus HTTP Beta3 has hit Central so I'm closing this one.

@gsmet gsmet closed this Oct 29, 2019
@gsmet gsmet added the triage/invalid This doesn't seem right label Oct 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage/invalid This doesn't seem right
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants