GNU bug report logs - #71295
29.3; url-retrieve-synchronously does not timeout if initial connection hangs

Previous Next

Full log

Message #20 received at 71295 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Dmitry Gutov <dmitry <at> gutov.dev>
Cc: z <at> bcc32.com, 71295 <at> debbugs.gnu.org, azeng <at> janestreet.com
Subject: Re: bug#71295: 29.3; url-retrieve-synchronously does not timeout if
 initial connection hangs
Date: Fri, 07 Jun 2024 09:20:11 +0300

> Date: Thu, 6 Jun 2024 23:41:39 +0300
> Cc: 71295 <at> debbugs.gnu.org, azeng <at> janestreet.com
> From: Dmitry Gutov <dmitry <at> gutov.dev>
> 
> On 06/06/2024 14:40, Eli Zaretskii wrote:
> >> This is probably rather naive of me, but I guess now I'm wondering why url-retrieve-synchronously actually sets url-asynchronous to nil.  Is there a good reason not to use :nowait when it is available?  It seems like it would be useful to have a wrapper around url-retrieve that just "does what I mean" here.
> > Maybe.  I wonder what others think about this.
> 
> It seems like a leaky abstraction (the caller has to be aware that what 
> happens under the covers is done in several steps, and the timeout only 
> applies to subsequent ones).
> 
> If we could change the implementation to a more intuitive behavior, that 
> would be a win, I think. Can somebody think of adverse effects?

Do you have a patch to consider?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.