>>From the BeOS demo I saw, I gathered that BeOS has one thread per top
>level frame window, not for every window whatsoever in the strict
>sense. But I may have misunderstood, there was, sadly, more hype than
>technical detail although some key developers were there and the demo
>was at MIT.
Andrew Vanderstock said:
(from <URL:http://er4www.eng.ohio-state.edu/~cooperb/kde/behavior.html>
* always available human interface. BeOS has at least two threads per
application - one to drive the interface, and one to drive the main().
This allows you to do actual work, whilst leaving the interface free for
interaction. It gives the user an impression that machine is really fast,
but all that's really happening, is that the user interface is always
available. We should also have the two-threads per application idea from
the word go.
***
That's definitely _not_ requisite of 1500 threads.
Wil
-------------------------------------------------------------
W. Reilly Cooley
NakedApe Consulting & Navi.Net representative
1509 NE 10th Ave., #104 Portland, OR 97232
503 287-2165 wcooley@navi.net
www.navi.net/~wcooley www.navi.net/~nakedape
As a service, I provide analysis for viruses and poor grammar to senders
of unsolicited commercial e-mail at a rate of US$250 per hour. Delivery of
said correspondence constitutes a request for the aforementioned services
at said price.