🚀 go-pugleaf

Christopher C. Wood <christw@meaddata.com> wrote:
: Comp.sys.intel deleted.

: In article <4glem9$li5@nnrp1.news.primenet.com>, Lawson English <english@primenet.com> writes:

: |> Nope to both (sorta). *ALL* applications that have a (an?) human
: |> interface must sit in the "BLue Box" and effectively, they
: |> cooperatively multitaslk WITH EACH OTHER (but see below about what
: |> "effectively" means).

: A Copland-savvy application spawns a separate process for the
: application's real work, leaving _only_ the user-interface portion
: running in the Blue Box.  So the application processing
: (e.g. background download in an FTP or web application, rendering,
: compression or decompression) is fully preemptive.


No. Copland-savvy applications CAN spawn a seperate process(s) for the 
application's  real work. You could factor the work-load any way you like.

Even Apple programmers are hazy on some of these details (I've had 
discussions with some promiment ones on AIMED-talk and in e-mail, so I 
know this for a fact) since not all Apple programmers are designing 
around Copland yet. If you have NDA information that contradicts what 
I've suggested above, that's fine, but even the gurus from Apple, unless 
they are directly involved in COpland design, haven't seen fit to 
contradict me here.


: |> There is no "protected memory" with Blue Box tasks, so if one goes
: |> down, they all may. 

: A process spawned by a blue box task doesn't go down.  And it can
: restart its UI portion.  Copland applications survive a blue box crash
: or lockup.  Copland applications have memory protection and preemptive
: multitasking. 


That may well be, if you've written  into the secondary task that you 
want it to monitor and restart the primaray (Blue Box/HI task) task that 
spawned it.

If that isn't part of the non-Blue Box API, it should be, and I'll throw 
it out into the aimed-talk discussion on high-level API's. Thanks.



BTW, are you familiar with any issues concerning pre-emptive threads in 
the same memory space of the Blue Box vs non-pre-emptive threads vs 
pre-emptive threads with their own memory space vs secondary tasks?

This appears to be an issue where all the APple folks (not under NDA) 
that I've talked to appear to be hazy.

Another interesting thing that I've learned is that the event loop goes 
away with Copland (save for backwards compatibility with older Apps) and 
that you instead install tables of event handlers ala AppleScript or 
OpenDoc...

--
-------------------------------------------------------------------------------
Lawson English                            __  __     ____  ___       ___ ____
english@primenet.com                     /__)/__) / / / / /_  /\  / /_    /
                                        /   / \  / / / / /__ /  \/ /___  /
-------------------------------------------------------------------------------