🚀 go-pugleaf

In article <132607@sun.Eng.Sun.COM> hvr@sun.UUCP (Heather Rose) writes:
>Is there a way to allocate server pixmaps as sharable objects?  i.e. one
>client allocates a pixmap as "read-only" so other clients could use it.
>That would make the problem much easier to solve.
Yes.  I did it for xtrek sometime last year (I mucked around w/ xtrek so much
it needed around 300 pixmaps, and there was a full second pause anytime anyone
new was added to the game...).

From what I remember: do access checks change the shutdown mode to (someting
like) RetainPerminant, create Pixmaps (and any other perminant objects), then
hang a property off the root window called XTREK_PIXMAPS which should be
created to be of type PIXMAP (or XA_PIXMAP, or someting like that), contact
tell the xtrek server to go for it, then exit.  O, of corse if there was aready
a XTREK_PIXMAPS and it had the right number of Pixmaps I skiped the creation
step (unless given a force-it argument).
(there is also a RetainTempory that can be used to remove things when you are
done, but something seemed wrong about it so I ignored it).

For XView you will probbly want to fork off a process that exec's a program to
create the Pixmaps.
-- 
           stripes@eng.umd.edu          "Security for Unix is like
      Josh_Osborne@Real_World,The          Mutitasking for MS-DOS"
      "The dyslexic porgramer"                  - Kevin Lockwood
"Don't try to change C into some nice, safe, portable programming language
 with all sharp edges removed, pick another language."  - John Limpert