Add es_enable_webtransport
The first step to support WebTransport is for the server/client to send the setting SETTINGS_ENABLE_WEBTRANSPORT.
This support can be exposed as an Engine Setting, like the two other settings are.
Then in maybe_send_settings in lsquic_full_conn.c this should be read and appended to the outgoing SETTINGS frame.
Does this sound like a reasonable first step? If we can manage this, then lsquic will at least be able to receive and establish a WebTransport session (but more work is need to establish proper WebTransport streams under this session).
I can probably PR this if it sounds reasonable.
Sounds great! When will it be done in Lsquic release?
Hi
The first step to support WebTransport is for the server/client to send the setting SETTINGS_ENABLE_WEBTRANSPORT.
This support can be exposed as an Engine Setting, like the two other settings are.
Then in maybe_send_settings in lsquic_full_conn.c this should be read and appended to the outgoing SETTINGS frame.
Does this sound like a reasonable first step? If we can manage this, then lsquic will at least be able to receive and establish a WebTransport session (but more work is need to establish proper WebTransport streams under this session).
I can probably PR this if it sounds reasonable.
Hi Alex Any update about this PR? Really looking forward to it.
Since it is a big change, we can create a branch for webtransport, and accept pull requests there.
Since it is a big change, we can create a branch for webtransport, and accept pull requests there.
Thanks for your reply, and when should this PR be done?
It is up to the person who submits the pull request.