Skip to content

RFC: Demonstration of http2-jetty, http3-jetty & http2-robaho#331

Draft
mechite wants to merge 2 commits intoavaje:masterfrom
mechite:master
Draft

RFC: Demonstration of http2-jetty, http3-jetty & http2-robaho#331
mechite wants to merge 2 commits intoavaje:masterfrom
mechite:master

Conversation

@mechite
Copy link
Collaborator

@mechite mechite commented Dec 2, 2025

@SentryMan
Related-to: #46
Signed-off-by: Mahied Maruf contact@mechite.com

Signed-off-by: Mahied Maruf <contact@mechite.com>
@mechite mechite marked this pull request as draft December 2, 2025 15:59
@mechite
Copy link
Collaborator Author

mechite commented Dec 2, 2025

If in the Jetty one, we don't use JettyHttpServerProvider.setServer, and instead make
our own provider, we could completely evade static configuration, meaning one can
have two Jetty servers running using Jex, with independent configuration

This seems trivial to do

EDIT — I will probably work on this more later, but I'm quite busy ATM

@SentryMan
Copy link
Collaborator

SentryMan commented Dec 3, 2025

yeah the jetty spi is nonfunctional with http2/http3 atm

@mechite
Copy link
Collaborator Author

mechite commented Jan 30, 2026

@SentryMan what kind of test do we even write here?

  • The robaho one:
    • sets the http2 system prop
    • sets Jex serverProvider to robaho.net.httpserver.DefaultHttpServerProvider
  • The jetty ones:
    • configure JettyHttpServerProvider for http2 and http3 respectively
    • set Jex serverProvider to it

if you have any idea feel free to put a trivial test even if it fails
I'll take a look later

@SentryMan
Copy link
Collaborator

the robaho one is so simple I don't think we need a test, for jetty, what's needed is to make even a basic get call

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants