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

Leverage platform http service #184

Closed
lburgazzoli opened this issue Sep 5, 2019 · 6 comments
Closed

Leverage platform http service #184

lburgazzoli opened this issue Sep 5, 2019 · 6 comments
Assignees
Milestone

Comments

@lburgazzoli
Copy link
Contributor

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.

  • quarkus --> vertx-web
  • spring --> ???
  • widfly --> undertow/servlet

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.

@ppalaga
Copy link
Contributor

ppalaga commented Sep 5, 2019

Sounds reasonable. Feel free to assign to me.

@ppalaga
Copy link
Contributor

ppalaga commented Sep 5, 2019

BTW, what is the relationship to the new quarkus router engine?

@lburgazzoli lburgazzoli added this to the 1.0.0 milestone Sep 5, 2019
@ppalaga
Copy link
Contributor

ppalaga commented Sep 9, 2019

How should the URI scheme be called? http-server maybe?

@ppalaga
Copy link
Contributor

ppalaga commented Sep 13, 2019

How should the URI scheme be called? http-server maybe?

Going with platform-http after a discussion with @lburgazzoli

ppalaga added a commit to ppalaga/camel-quarkus that referenced this issue Sep 13, 2019
ppalaga added a commit to ppalaga/camel-quarkus that referenced this issue Sep 13, 2019
ppalaga added a commit to ppalaga/camel-quarkus that referenced this issue Sep 13, 2019
ppalaga added a commit to ppalaga/camel-quarkus that referenced this issue Sep 13, 2019
ppalaga added a commit to ppalaga/camel-quarkus that referenced this issue Sep 17, 2019
ppalaga added a commit to ppalaga/camel-quarkus that referenced this issue Sep 17, 2019
ppalaga added a commit to ppalaga/camel-quarkus that referenced this issue Sep 17, 2019
ppalaga added a commit to ppalaga/camel-quarkus that referenced this issue Sep 17, 2019
ppalaga added a commit to ppalaga/camel-quarkus that referenced this issue Sep 27, 2019
ppalaga added a commit to ppalaga/camel-quarkus that referenced this issue Sep 27, 2019
ppalaga added a commit to ppalaga/camel-quarkus that referenced this issue Sep 27, 2019
ppalaga added a commit to ppalaga/camel-quarkus that referenced this issue Oct 1, 2019
ppalaga added a commit to ppalaga/camel-quarkus that referenced this issue Oct 1, 2019
ppalaga added a commit to ppalaga/camel-quarkus that referenced this issue Oct 1, 2019
@davsclaus
Copy link
Contributor

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.

@lburgazzoli
Copy link
Contributor Author

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)

davsclaus added a commit that referenced this issue Oct 3, 2019
Fix #184 Leverage platform http service
JiriOndrusek added a commit to JiriOndrusek/camel-quarkus that referenced this issue Oct 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Platform integration
Awaiting triage
Development

No branches or pull requests

3 participants