Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Asynchroneous image retrieval in HTML rendering
Date: Thu, 05 May 2011 08:51:47 -0500	[thread overview]
Message-ID: <87k4e5z24s.fsf@lifelogs.com> (raw)
In-Reply-To: <87tyd9jt0r.fsf@gmail.com>

On Thu, 05 May 2011 13:17:40 +0200 Antoine Levitt <antoine.levitt@gmail.com> wrote: 

AL> 05/05/11 12:48, Ted Zlatanov
>> On Mon, 02 May 2011 19:40:43 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote: 
>> 
LMI> The next thing to tackle is doing the DNS resolving asynchronously.
>> ...
LMI> If only somebody could implement an async C-level resolver.  :-)
>> 
>> On Thu, 05 May 2011 10:25:15 +0200 Julien Danjou <julien@danjou.info> wrote: 
>> 
JD> http://www.corpit.ru/mjt/udns.html
>> 
>> On Wed, 04 May 2011 20:40:58 +0200 Simon Josefsson <simon@josefsson.org> wrote: 
>> 
SJ> http://www.chiark.greenend.org.uk/~ian/adns/
>> 
>> Has anyone tested to see if DNS lookups are actually a problem?  Test an
>> entirely local page vs. a page with lots of remote image URLs.  I don't
>> see a difference on my machine.

AL> Maybe your connexion or DNS servers are better than mine, or some other
AL> parameter is different, but I definitely experienced freezes that were
AL> DNS-related. Lars also pointed out explicitely resolving the DNS in
AL> /etc/hosts sped things up immensely for gwene.com.wordpress.terrytao, so
AL> you could try this if you're not convinced by my admitedly
AL> non-repeatable arguments.

OK.

>> Typically DNS lookups are very fast and HTML pages don't have a huge mix
>> of domains for the images they reference, so I think this is wasted
>> effort *for the specific purpose of rendering HTML faster*.  I can't
>> think of any practical uses within Emacs for async DNS lookups,
>> either.

AL> I don't know why, but DNS results don't seem to be cached. I don't know
AL> much about DNS queries so I'm not sure if that's supposed to be the case
AL> or not.

It's configurable and depends on the DNS records, but typically they
have a TTL of at least an hour.

On Thu, 05 May 2011 12:58:24 +0200 Julien Danjou <julien@danjou.info> wrote: 

JD> I may be wrong, but I disagree: they are usually fast, except when there
JD> is a problem or you're behind a very slow link. Just because they are
JD> serialized and synchronous.

OK, I'll buy that (and Antoine's argument above).

JD> OTOH, I agree that the only useful place for this enhancement is
JD> probably HTML rendering…

There are some DNS-based anti-spam services but I can't think of
anything else that might require it.

Ted




  reply	other threads:[~2011-05-05 13:51 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-23 22:18 Antoine Levitt
2011-04-28 20:03 ` Antoine Levitt
2011-04-29  9:04 ` Julien Danjou
2011-04-29  9:18   ` Antoine Levitt
2011-04-29 10:01     ` Julien Danjou
2011-04-29 20:34       ` Antoine Levitt
2011-05-01 15:13         ` Lars Magne Ingebrigtsen
2011-05-01 15:23           ` Antoine Levitt
2011-05-01 15:42             ` Lars Magne Ingebrigtsen
2011-05-01 16:06               ` Lars Magne Ingebrigtsen
2011-05-01 16:34                 ` Adam Sjøgren
2011-05-01 16:45                   ` Lars Magne Ingebrigtsen
2011-05-01 17:15                 ` Antoine Levitt
2011-05-02  7:52               ` Antoine Levitt
2011-05-02 14:30                 ` Lars Magne Ingebrigtsen
2011-05-02 14:53                   ` Antoine Levitt
2011-05-02 15:17                     ` Lars Magne Ingebrigtsen
2011-05-02 17:08                   ` Lars Magne Ingebrigtsen
2011-05-02 17:24                     ` Antoine Levitt
2011-05-02 17:40                       ` Lars Magne Ingebrigtsen
2011-05-02 21:52                         ` Antoine Levitt
2011-05-04 18:40                         ` Simon Josefsson
2011-05-30 20:55                           ` Lars Magne Ingebrigtsen
2011-05-05  8:25                         ` Julien Danjou
2011-05-30 20:56                           ` Lars Magne Ingebrigtsen
2011-05-05 10:48                         ` Ted Zlatanov
2011-05-05 10:58                           ` Julien Danjou
2011-05-05 11:17                           ` Antoine Levitt
2011-05-05 13:51                             ` Ted Zlatanov [this message]
2011-05-05 14:01                             ` David Engster
2011-05-05 14:07                               ` Julien Danjou
2011-05-05 15:05                               ` Lars Magne Ingebrigtsen
2011-05-05 19:49                                 ` David Engster
2011-05-05 20:07                                   ` Lars Magne Ingebrigtsen
2011-05-05 14:25                             ` David Engster
2011-05-05 14:34                               ` Antoine Levitt
2011-05-05 14:59                                 ` David Engster
2011-05-05 15:00                                   ` David Engster
2011-05-02 17:53                       ` Lars Magne Ingebrigtsen
2011-05-02 18:18                         ` Lars Magne Ingebrigtsen
2011-05-02 17:12                   ` Ted Zlatanov
2011-05-02 17:20                     ` Lars Magne Ingebrigtsen
2011-05-02 21:18                       ` Steinar Bang
2011-05-02 22:40                         ` Lars Magne Ingebrigtsen
2011-05-03 14:09                           ` Ted Zlatanov
2011-05-03 18:48                             ` Steinar Bang
2011-05-02 21:15                   ` Steinar Bang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k4e5z24s.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).