Re: multithreaded libwww
Garrett Arch Blythe <doslynx@falcon.cc.ukans.edu>
Errors-To: listmaster@www0.cern.ch
Date: Thu, 12 May 1994 21:08:26 +0200
Errors-To: listmaster@www0.cern.ch
Message-id: <Pine.3.05.9405121344.B5887-b100000@falcon.cc.ukans.edu>
Errors-To: listmaster@www0.cern.ch
Reply-To: doslynx@falcon.cc.ukans.edu
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: Garrett Arch Blythe <doslynx@falcon.cc.ukans.edu>
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: Re: multithreaded libwww
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Type: TEXT/PLAIN; charset=US-ASCII
Mime-Version: 1.0
Mime-Version: 1.0
On Thu, 12 May 1994, Henrik Frystyk Nielsen wrote:
> Reply to Pei:
>
> >>>>>>>>>>
> Anyone working on making libwww to be multi threaded? Tim?
>
> -Pei
>
> <<<<<<<<<<
>
> YES! I have started the conversion bit by bit to make the CERN WWWlib
> multi-threaded on the client side. Though, I am making it in parallel with a
> lot of other things, but my plan is to get it ready for a release 2.16.
>
> Any ideas or suggestions are welcome!
By multi-threaded, I take it you mean having multiple documents
you can pull up and take them in the direction that you want independent
of the other loaded documents.
If this is the case, then by all means take a look at DosLynx,
which uses a MDI (multiple document interface) to handle this type of
multi-threading. It does this with CERN WWWlib 2.14 with no special
modifications to the library.
All considerations regarding multi-threading are handled by the
client by making the functions in GridText.c take special care on where
their screen output is sent specific to the HText object currently being
rendered.
Garrett.
Trodden Soil
I am trodden soil.
Dust covers my face.
Soles crush my nature
Revealing a hard empty space.
Garrett Arch Blythe (913)864-0465
User Services Student Programmer/Consultant
University of Kansas Computer Center