home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!sun-barr!sh.wide!wnoc-tyo-news!scslwide!wsgw!wsservra!daemon
- From: rjc@cogsci.ed.ac.uk (Richard Caley)
- Newsgroups: fj.mail-lists.x-window
- Subject: Re: FLAME, FLAME ON X!!!
- Message-ID: <1992Nov20.092423.22012@sm.sony.co.jp>
- Date: 20 Nov 92 09:24:23 GMT
- Sender: daemon@sm.sony.co.jp (The devil himself)
- Distribution: fj
- Organization: Human Communication Research Center
- Lines: 21
- Approved: michael@sm.sony.co.jp
-
- Date: 19 Nov 92 15:32:29 GMT
- Message-Id: <RJC.92Nov19153229@daiches.cogsci.ed.ac.uk>
- Newsgroups: comp.windows.x
- References: <1dn1c7INNcnp@armory.centerline.com>, <1992Nov10.173203.10719@dsd.es.com>
- Sender: xpert-request@expo.lcs.mit.edu
-
- In article <1992Nov17.195218.27789@netcom.com>, Qual Trak (qt) writes:
-
- qt> If the client asks the server to make him a window - the server
- qt> allocates the memory, not the client.
-
- ???
-
- Sorry, I don't see your point. the problem mentioned _was_ server
- growth, so server-memory fragmentation is one possible problem. The
- clients, in the case described, were going away and being restarted,
- fragmentation there is obviously a non-problem.
-
- --
- rjc@cogsci.ed.ac.uk _O_
- |<
-