On Sat, Dec 10, 2022 at 4:59 PM Shawn Heisey wrote:
>
> On 12/9/2022 2:12 PM, Aryeh Friedman wrote:
> > For example the following code works against port 7 (UDP echo service)
> > but not against 8080 (my local tomcat):
>
> I suspect that you are running into the fact that HTTP/3 *always* uses
> TLS. It's baked into the protocol and NOT optional as with earlier HTTP
> versions. As far as I know, HTTP/3 is the only version of HTTP that
> uses UDP transport.
Is there any browser support for direct UDP sockets in any browser
besides Chrome? I know WebRTC and Websockets force TCP. I know
Chrome does support UDP but can find no evidence one way for the other
browsers.
Due to my soon forthcoming project being a streaming media site, true
real time delivery is the most important thing, and from my past work
as a protocol designer, I can say without any qualification that TCP
is absolutely the wrong protocol (there are other good end-to-end
reliable UDP protocols besides QUIC).
As far I can tell there are no web servers and/or major hosting
companies (i.e. AWS, etc.) that support UIUC/HTTP3. For that reason,
I am playing with different options for making a stripped down UDP
HTTP server (prefer 3 but forcing TLS seems to be a deal breaker for
anyone except name brand sites like Google -- E.g. my main client had
a total cow over the $500/yr fee for a Comodo multi-domain cert even
though due to being healthcare it is a legal requirement.)
--
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
