🚀 go-pugleaf

"Frank Nichols" <fnichols@earthlink.net> wrote:


>--Cyberdog-AltBoundary-00001
>Content-Type: text/plain; charset=US-ASCII
>Content-Transfer-Encoding: quoted-printable

>..in the still of the night, for our enlightenment and entertainment -=
> 

>scribed upon his computer - 


>>I understand that. But it looks to me as if it's impossible for an
>>application to run entirely outside of the Blue Box. So what I said
>>originally still seems right to me. If I'm wrong, show me how.
>>

>Try this, I agree there is still a small window where the application i=
>s vunerable in the blue box, but what if the "Application" which gets l=
>aunched is simply a loader which loads the "real" application into a se=
>parate process (server process). This process then laods a GUI shell in=
>to the blue box. Then as the application is running it occasionally che=
>cks the state of the BB and if there is a problem with its GUI part it =
>shuts it down and reloads a new one. To the user the GUI would appear t=
>o be "crash proof". Of course the application would need to maintain "s=
>tate" information about the GUI so the restart would appear bumpless.

Actually, it is possible to write an application that runs entirely
outside the Blue Box. They are sometimes referred to as "Faceless
Background Apps" - things such as finger daemons, file servers, web
servers, telnet daemons can work this way. (Actually there are some
that do this now - applications of File Type 'appe' do this.

In Copland they will be fully preemptive, protected - which will
further strengthen the Mac's ability to be a WWW server, file server,
etc.