On Fri, 10 Feb 2023, Dmitry Karpov via curl-library wrote:
- Provide the "system" layer functionality.
We've touched on this before, yes. I think it would be helpful to come up with more details and write down how this would work, perhaps from a user's perspective. I think that could help potentially getting more people interested.
- Provide TTL honoring for DNS cache entries for those DNS backends that provide the TTL information (like c-ares).
I consider that more or less just a bugfix, but yeah we should do that. Perhaps with a lower end cap, as sometimes the set TTL is just a couple of seconds.
Firefox has (had?) an interesting implementation solution where they use the system resolver to get the name but they also fire off a separate DNS lookup (like we could do with c-ares) to get only the TTL for improved cache time information from that separate API.
- Provide background buffering for H3/QUIC to match TCP socket background buffering.
I think this is a premature design idea, but I would fold this into a larger "make sure HTTP/3 transfers are as fast as possible" item once they actually are stable and made non-experimental.
- Eventually provide "message" layer support for WebSockets in libcurl.
I hope to get to this within 2023. -- / daniel.haxx.se | Commercial curl support up to 24x7 is available! | Private help, bug fixes, support, ports, new features | https://curl.se/support.html -- Unsubscribe: https://lists.haxx.se/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.html
