On Wed Jun 5 23:33:45 2024 +0000, Jacek Caban wrote:
Setting the timeout on the socket is quite expensive (requires a wineserver call). Maybe we could store the last set timeout separate from configure timeout and update socket timeout only when they don't match?
Would this proposal be only for `read_more_data` or in the broader scope of any call to `NETCON_set_timeout`?
If it is for the latter, it could be tracked in `netconn_t`. I can add that into a separate merge.