[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] patch:MiNT:KM_FREE



On Tue, Dec 15, 2009 at 6:40 PM, Jo Even Skarstein <joska@online.no> wrote:
> --------------------------------------------------
> From: "Paul Wratt" <paul.wratt@gmail.com>
> Sent: Tuesday, December 15, 2009 7:55 AM
> To: "mint" <mint@lists.fishpool.fi>
> Subject: Re: [MiNT] patch:MiNT:KM_FREE
>
>> With AES binding programs as child processes, it may in fact be
>> possible to run two odf them, It will be interesting to see how
>
> How? They both use the same TRAP, how do you want to direct the calls to the
> correct AES? And what would be the advantage of running more than one AES?
> Also, you need to have one physical workstation for each instance of the
> AES.
>
>> AVSERVER reacts to this, or can be accomodated. I have a raw AVSERVER
>> somewhere, of one of the uptodate ftps, it will probably work well in
>> this situation if loaded before and AES, as it does not have any
>> graphics stuff (desktop etc)..
>
> It won't work if loaded before the AES. An AV-server is an AES-application
> and thus needs a running AES.
>
> If you can solve the TRAP-problem, and the physical workstation problem, the
> AV-server will work just fine. But I still wonder what the purpose of this
> is.
>
> Jo Even
>
instant per app themes (without the work, well in theory.) running
from different/multiple desktops to allow a dev environment and its
associated differences to be used, possibly in conjunction with a
regular desktop.

I have already experimented with multiple desktops, it is possible,
but I did not test the practical side of it, yet... different AES
would make it even more visually distinctive..

It is also a test worth doing, particularly if, as you say, "If you
can solve the TRAP-problem, and the physical workstation problem"

It may be useful later on for VNC and remote desktop "assistance" and
VDI/AES streaming over TCP/IP (or UDP), as one "AES/desktop" can
remain untouched.. It could solve the problem of multiple user logons
with different AES and desktop settings (for systems that can handle
it and use it). It would be a good "proof of concept" test at least,
even if it were not immediately practical.

Paul