[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev "display partial" implementation in 'links'
From: |
Mikulas Patocka |
Subject: |
Re: lynx-dev "display partial" implementation in 'links' |
Date: |
Sun, 5 Dec 1999 01:24:45 +0100 (CET) |
> > > Relying on threads of course means it can never be as portable as lynx.
> > > Forget about a DOS port, a VMS port, ...
> >
> > It uses fork-and-pipe method for simulating threads. Is this method
> > unavailable on VMS?
>
> yes.
Links doesn't use threads. It's based completely on select(). It forks (on
Unix) or spawns thread (on OS/2) only when it needs to do lookup (can be
avoided with option -async-lookup 0) or when it spawned some user viewer
and needs to wait() for it. fork/thread routines are very simple, they
don't touch any global variables and thus the same routine can be run from
a fork()ed child or a thread.
Mikulas
Re: lynx-dev "display partial" implementation in 'links', T.E.Dickey, 1999/12/03
Re: lynx-dev "display partial" implementation in 'links', T.E.Dickey, 1999/12/04
Re: lynx-dev "display partial" implementation in 'links',
Mikulas Patocka <=