Re: multithreaded libwww

• Mail folder: WWW Talk Apr 94-present
• Next message: Rick Troth: "Re: Performance analysis questions "
• Previous message: Pei Y. Wei: "Re: multithreaded libwww"

Errors-To: listmaster@www0.cern.ch
Date: Fri, 13 May 1994 13:52:36 +0200
Errors-To: listmaster@www0.cern.ch
Message-id: <9405131146.AA08715@hummingbird.syl.nj.nec.com>
Errors-To: listmaster@www0.cern.ch
Reply-To: pel@syl.nj.nec.com
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: pel@syl.nj.nec.com
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: Re: multithreaded libwww 
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Mailer: exmh version 1.3delta 3/31/94
X-Mailer: exmh version 1.3delta 3/31/94

>Garrett Arch Blythe <doslynx@falcon.cc.ukans.edu>:
>>         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.
>
>Specifically, I'm looking forward to the WWW library being able to handle
>multiple independent time/cpu-sliced HTTP operations. This way, a browser
>doesn't have to halt all user interactions (save the HTTP interupt) until
>after all HTTP operation is completed or interrupted. 
>
>With threading, for example, you would be able to read/scroll/following-links
>in a page-screen, while another screen is busy doing HTTP "in the background".


Don't forget, this may also require a multi-threaded  Xt and Motif library
to get everything right.  Yes R6 has the beginnings of threaded-ness but
I don't think Xm does.

--
Paul Leclerc            NEC Systems Laboratory          Voice:  609-734-6147
pel@syl.nj.nec.com      4 Independence Way              FAX:    609-734-6002
                        Princeton, NJ  08540