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
Leverage platform http service #184
Comments
Sounds reasonable. Feel free to assign to me. |
BTW, what is the relationship to the new quarkus router engine? |
How should the URI scheme be called? |
Going with |
Btw is there anything that makes this http-platform component quarkus specific? I am asking as it may be something we should eventually move to upstream main Camel so it can be used elsewhere too. |
There is a SPI for platform specific code so yes, the component should be moved to mian Camel as soon as the SPI is stable enough (there is still some work to be done to i.e. make this component usable for the rest dsl) |
Fix #184 Leverage platform http service
As today to leverage the http service provided by quarkus we do rely on
servlet
but we can do much better and bypass the servlet engine.To do so we need to create a sort of "platform http component" that leverage what the platform camel runs on has to offer i.e.
I would start by creating such component and quarkus binding here and once we have a stable enough API we can move the common part to main camel repository.
The text was updated successfully, but these errors were encountered: