[interfacekit] Re: Proposal: Only one thread per application(not window) o= n app_server side without polling
- From: "Ingo Weinhold" <bonefish@xxxxxxxxxxxxxxx>
- To: interfacekit@xxxxxxxxxxxxx
- Date: Tue, 29 Jul 2003 15:32:13 +0200 CEST
On Tue, 29 Jul 2003 15:43:06 +0300 "Adi Oanca" <adioanca@xxxxxxxxxxxxx>
wrote:
> > > app side rendering is a nice idea as it would reduce the load on
> > > the
> > > app_server, which in turn would 'just' have to coordinate shared
> > > resources.
> > > Clearly hardware acceleration must be available on the app side.
> >
> > I don't think, it's a good idea to move too much functionality of
> > the
> > app server into the applications. A clear client/server approach
> > will
> > e.g. make it easier to transparently implement the feature of
> > running
> > remote applications.
>
> NOT that I agree moving AS functionality in libbe, but in case of
> remote
> GUI app running, app_server would be in local memory, won't he?
The one responsible for rendering on your local screen certainly does.
How the connection from the remote application to it works, remains to
be designed. E.g. the app server on the remote machine could act as a
proxy.
> One other thing I do not like - or I might be wrong - is that by
> copying
> rendering code(with all its components) - be it for bitmap rendering
> only -
> into libbe, would increase considerably the memory footprint of an
> app with
> a few windows, thus minimizing the number of applications that can be
> launched.
I'm not sure, what kind of memory usage you're thinking of here.
Supposedly physical memory. But whether the drawing code for bitmaps
resides in libbe or the app server executable has no impact on physical
memory. The libbe code resides in shared memory.
> > The proposal for drawing non-off-screen bitmaps on
> > the application side does explicitly draw only bitmaps, that can be
> > draw locally, on the app side.
>
> What are you trying to say here...?
Only that rendering bitmaps in the application wouldn't stand in the
way of running applications remotely, since one can simply do the
drawing in the app server in this case (though I think, that wouldn't
even be necessary).
CU, Ingo
Other related posts: