Re: [GNUnet-developers] libwget2

Yes, I also recall that the fact that libwget2's support for event loops was insufficient despite the kitchen-sink was the killer issue for me as well when I last looked at the header. On 03/23/2018 08:25 AM, Schanzenbach, Martin wrote: > I don't see this playing nice with the GNUnet scheduler.

Re: [GNUnet-developers] libwget2

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) does internal

Re: [GNUnet-developers] libwget2

Hi, I guess one thing is that we need (gn|c)url for other things than downloading (e.g. proxying see gns). Can wget do other things? A brief look at the API makes me doubt that. If not, then wget2 is just another additional dependency. BR > On 22. Mar 2018, at 19:13, ng0 wrote: >

[GNUnet-developers] libwget2

Hi, remind me again: What exactly is in the way (besides us making relevant changes in GNUnet) to make use of libwget2 as a successor to gnURL? Someone knew it and had just grumpy opinions on the wget.h ... but besides "omg it is long", what can we do in cooperation with wget2 to get to a point