From: Julien Danjou <julien@danjou.info>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: Asynchroneous image retrieval in HTML rendering
Date: Thu, 05 May 2011 12:58:24 +0200 [thread overview]
Message-ID: <sa31v0d1kj3.fsf@cigue.easter-eggs.fr> (raw)
In-Reply-To: <87k4e5h18p.fsf@lifelogs.com> (Ted Zlatanov's message of "Thu, 05 May 2011 05:48:22 -0500")
[-- Attachment #1: Type: text/plain, Size: 933 bytes --]
On Thu, May 05 2011, Ted Zlatanov wrote:
> 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.
In a web browser? Because they are parallelized and/or multi-threaded,
maybe?
> 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.
I may be wrong, but I disagree: they are usually fast, except when there
is a problem or you're behind a very slow link. Just because they are
serialized and synchronous.
OTOH, I agree that the only useful place for this enhancement is
probably HTML rendering…
--
Julien Danjou
❱ http://julien.danjou.info
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2011-05-05 10:58 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 [this message]
2011-05-05 11:17 ` Antoine Levitt
2011-05-05 13:51 ` Ted Zlatanov
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=sa31v0d1kj3.fsf@cigue.easter-eggs.fr \
--to=julien@danjou.info \
--cc=ding@gnus.org \
--cc=tzz@lifelogs.com \
/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).