gnunet-developers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [GNUnet-developers] libwget2


From: Christian Grothoff
Subject: Re: [GNUnet-developers] libwget2
Date: Fri, 23 Mar 2018 13:34:30 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0

On 03/23/2018 01:04 PM, ng0 wrote:
> Hi,
> 
> Schanzenbach, Martin transcribed 3.7K bytes:
>> So. Christian is a bit better with those things but I have just taken a 
>> brief look into wget2.
>> The thing is that curl has a "nice" way of having your own scheduling (using 
>> curl_multi_perform etc).
>> As far as I can see wget2 (apart from having a _huge_ kitchensink as well) 
> 
> Wasn't the kitchensink one of the reasons to consider switching away from 
> curl? Now I'm curious
> for what Christian sees in wget2.

Curl has kitchensink *dependencies* (run 'ldd' on libcurl.so), but a
relatively small API.

Wget2 has small dependencies, but a large API.

Still, the Curl API works with an (external) event loop in a
non-blocking way, while Wget2 cannot do that.

>> does internal multithreading for downloads in connections and almost 
>> exclusively has blocking, synchronous calls.
>> Even in their async example the calls are blocking! See 
>> https://github.com/rockdaboot/wget2/blob/master/examples/http_multi_get.c.
>> (Maybe there is way to implement proper async calls; possibly using 
>> wget_net*: 
>> https://gnuwget.gitlab.io/wget2/reference/group__libwget-net.html#ga71e02092659a35a26c8ac4cdfec23854)
> 
> And this is bad for us in GNUnet because we require non-blocking asyc calls?

Yes.

Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]