nanogui: make microwin api : client/server
Subject:
Re: make microwin api : client/server
From:
####@####.####
Date:
23 Apr 2000 08:41:02 -0000
Message-Id: <20000423012955.W14614@www.easysolutions.net>
Well,..., I'm a little concerned about not having that process
seperation between the server and the actual app. In fact quite
concerned. You're right... it would be a LOT of work, but isn't it
worth it? Well, maybe we're not ready for it. But I'm a little
skeptical at putting a lot of time/effort into the "module" loading
when it's not going to be the final solution. Shared memory pages
would be awesome..., but the MSDOS folk might not be able to use this.
Write the Client side stuff as just sharedmemory page manipulation,
and the Microwin server would just pull up changes from that. Could
anyone confirm as to whether X works like this when run "locally"?
That's what I thought, but could be totally wrong. Oh, yes and when
not in local mode it would function through some sort of network
interface thingee.
We want X functionality..., but we don't want to be X... this is the
enigma.
Thanks,
Shane.
On Thu, Apr 13, 2000 at 04:52:34PM -0600, Greg Haerr wrote:
> I plan on adding module-loading capabilities to the microwin
> api, which will allow multiple "applications" to use that API.
>
> Creating a full-blown client/server architecture involves LOTS
> of typing, unless we use a MIDL-like compiler that generates
> the client and server stub marshalling for us. This is required
> because win32 uses pointers in the API, unlike ID's in Nano-X.
>
> Regards,
>
> Greg
>
> ----- Original Message -----
> From: ´¿¬L©ú
> To: ####@####.####
> Sent: Tuesday, April 11, 2000 11:38 PM
> Subject: make microwin api : client/server
>
>
> question: make microwin api : client/server
> is there any "official" project to make microwin api : client/server
> thx in advanced!:)
>
