Messages in this thread |  | | | Subject | Threads Question | | Date | Fri, 25 Apr 1997 19:51:13 EDT | | From | Maciej Stachowiak <> |
| |
Jean-Philippe Langlois <jpl@iname.com> wrote: >Please don't apologize. I should have said that my project was really a >research/curiosity project. The _real_ thing is actually designed with >two threads in the most common case. One to handle the GUI with events >dispatched sequentially, and one to do the rest of the work. >My curiosity came from the BeOS, which I heard uses one thread per >window. When asked about the overhead in memory and cpu time for >switching contexts, they told me their threads where _really_ >lightweighted. But your remark made much sense, someone else also >mentioned 4MB os user stack as well. 8MB just for the threads' stacks >would be a ridiculous waste. Thanks for your input.
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.
- Maciej Stachowiak
|  |