[interfacekit] Re: Proposal: Only one thread per application (not window) o= n app_server side without polling

> > 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?
    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.

> 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...?




Other related posts: