9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Geoff Collyer <geoff@collyer.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] new links binary+source
Date: Wed, 17 Dec 2003 18:33:39 -0800	[thread overview]
Message-ID: <4232834834cb615e6196fd51ce05806e@collyer.net> (raw)
In-Reply-To: <6f9f894bbd181956d09c161d6e561004@granite.cias.osakafu-u.ac.jp>

Links is still quite slow on some pages, notably nytimes.com and
cnn.com.  I haven't looked into why, but I suspect it's not good at
retrieving lots of small images.  There are no doubt lots of bugs left
in links.  One workaround is to select "Kill all connections" from the
File menu and then go to that URL again.  Whatever has been cached
already should be displayed while it fetches the rest.

I believe Andrey did all the font work and the faster rendering.

The fundamental structure of links is just wrong: it tries to simulate
threads or processes sharing memory by using select to trigger
functions when input arrives, and using a convention that upon
completion of some activity, there's a always a `completion routine'
to be called next, possibly by select.  It would be better on Plan 9
to just rfork a process for each http request and let it run to
completion, but doing that may require doing considerable violence to
links (not that I'm opposed to that ☺).

A few of us are also looking at using webfs, at Russ's suggestion.
The more we can move out of links, the better.



  reply	other threads:[~2003-12-18  2:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-17 21:03 mirtchov
2003-12-17 21:23 ` Axel Belinfante
2003-12-18  2:16 ` okamoto
2003-12-18  2:33   ` Geoff Collyer [this message]
2003-12-18  2:52     ` okamoto
2003-12-19  6:10   ` okamoto
2003-12-19  6:20     ` andrey mirtchovski
2003-12-19  6:41       ` okamoto
2003-12-19 14:15         ` mirtchov
2003-12-19  6:49       ` okamoto

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=4232834834cb615e6196fd51ce05806e@collyer.net \
    --to=geoff@collyer.net \
    --cc=9fans@cse.psu.edu \
    /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).