Hi,
I already talked to Tim a year ago about this.
Unfortunately since GNU was not participating in GSoC this did not get
any traction. Neither me or Tim have (had?) the bandwidth to do this.
But in terms of requirements what we need first is what curl multi API
offers _including_ the curl_multi_
Hello everyone,
wget2 community is hearing our conversation and is reaching out to us for
collaboration:
story - short:
> On 10. Sep 2022, at 20:53, Tim Rühsen wrote:
>
> just found this issue: https://gitlab.com/gnuwget/wget2/-/issues/550
>
> Feel free to add the details needed for GNUnet.
Imagine that a "GET /download" downloads 1GB of data.
If your code looks like this (not the actual API but for demonstration
purposes):
data = wget_get("/download")
// Wait until download completes
Then you have a blocking API.
Instead you can have a non-blocking API that allows you to "select"
I never used the curl API, so I don't know what the multi interface is, but
if I remember correctly wget2 introduced non-blocking sockets. That's all I
know. I did not find a lot of info on Google, except maybe for this email
on gnutls mailing list:
https://lists.gnutls.org/pipermail/gnutls-devel/2
We need a non-blocking API such as curl_multi.
Last time I checked, libwget2 does not have that.
BR
> On 7. Sep 2022, at 15:46, madmurphy wrote:
>
> I don't know all the reasons behind using curl and all GNUnet's requirements,
> but have you guys thought about switching to wget2? It is a GNU p
I don't know all the reasons behind using curl and all GNUnet's
requirements, but have you guys thought about switching to wget2? It is a
GNU package and has a nice library (libwget). It supports GNU TLS natively,
it is supposed to download faster than curl, and if a minor feature is
missing it mig
