Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!ucsd!ucbvax!decwrl!shelby!med!hanauma!rick
From: rick@hanauma.stanford.edu (Richard Ottolini)
Newsgroups: comp.windows.x
Subject: Re: Use of backing store to prevent exposures
Keywords: new server architecture
Message-ID: <593@med.Stanford.EDU>
Date: 5 Mar 90 23:40:33 GMT
References: <188@trwacs.UUCP>
Sender: news@med.stanford.edu (USENET News System)
Reply-To: rick@hanauma.UUCP (Richard Ottolini)
Organization: Stanford University, Dept. of Geophysics
Lines: 14

In article <188@trwacs.UUCP> epstein@trwacs.UUCP (Jeremy Epstein) writes:
>(2)	Store the sequence of X protocol requests associated with the
>		window and replay it as needed.
>	Advantage: Minimal work required to store and replay the requests.
>	Disadvantage: Unless you understand exactly what every request does
>		and what it affects on the screen, you may have to replay
>		all events since the beginning of time, which would clearly
>		be slow!

Represent images at a higher level of abstraction than bitmaps or drawing
commands, preferably in terms of what things you are drawing.
Then you only need to redraw the currently active set of objects.
MacDraw is an early and widespread example of this philosophy.
The Unidraw toolkit in X Windows InterViews is good starting point.