walkor
Support for WebTransport
Hello @walkor
Since you're the most reliable person to ask such a question, do you plan to support WebTransport?
Any suggestions on what to use now if I want to have a WebTransport server?
Thanks @walkor
What do you recommend on how to move forward with currently?
Do you support sponsored development?
I'm not sure why you need WebTransport—perhaps WebSocket is already sufficient for your application?
I believe implementing HTTP3 (QUIC) + WebTransport purely in PHP would require significant effort. Perhaps finding an existing HTTP3 + WebTransport proxy service (though I'm not sure if such a solution exists) and then forwarding the data to Workerman might be a more feasible approach. Yes, I support sponsored development.
The primary goal is having a lightweight communication protocol for an application launching in countries with high latency and mostly unreliable Internet connections. The service this application is providing is a mission critical an important to be up and reachable in all conditions. WebTrabsport tends to be handling that out of the box already relying on QUIC/UDP, versus WebSockets.
Can you have a Quick Look at the latest RFC and tell me https://datatracker.ietf.org/doc/draft-ietf-webtrans-http3/
Not entirely sure, but MQTT-SN which operates over UDP would've been an option here but not sure if there's a PHP implementation for it.
Also, relying on WebTrabsport would allow for operating behind reverse proxies like Cloudflare and Fastly and alike.
That's why all fingers point towards WebTransport.
WebTransport, built on the QUIC/UDP protocol, appears more suitable for high-latency and unstable network environments, but its implementation in PHP is relatively complex. MQTT-SN serves as another solution for unreliable networks, but the lack of direct PHP client libraries makes it less feasible.
Well said and understood.
Which of these would you see as a fit for adding as a feature or engaging in a sponsored development?
How can we communicate private (if you prefer) regarding this?
Which of these would you see as a fit for adding as a feature or engaging in a sponsored development?
It's difficult to say, because I need to have a deeper understanding of your application needs, including the development languages and frameworks used on both the client and server sides, as well as whether your application client is based on a browser or other platforms. WebTransport is a relatively new technology that relies on the support of client browsers, and currently not all browsers support this feature. Additionally, the support from CDN platforms is also a consideration; for example, I have not seen any mention of WebTransport support in the official Cloudflare documentation.
I am open to private communication and can be reached via email at [email protected].
@akiirax what do you think that you need WebTransport ??
I'm usign SSE and is working perfect !! It's a consolidated technology working really good for a lot of my projects.
And remember the new thinks are not always the best !!
PD: if don't arrive an UDP also don't arrive a TCP !! and vice versa
