Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!bloom-beacon!oberon!cit-vax!ucla-cs!zen!ucbvax!BRILLIG.UMD.EDU!don
From: don@BRILLIG.UMD.EDU (Don Hopkins)
Newsgroups: comp.windows.news
Subject: fast bitmaps
Message-ID: <8710160550.AA23290@brillig.umd.edu>
Date: Fri, 16-Oct-87 01:52:40 EDT
Article-I.D.: brillig.8710160550.AA23290
Posted: Fri Oct 16 01:52:40 1987
Date-Received: Sat, 17-Oct-87 17:41:04 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 13

One thing you might experiment with is having your client write out a
pixrect file, then hand the server the file name, which it can read
with 'readcanvas', and then use 'imagecanvas', which is much faster
than 'image'. (This kind of stuff is one reason that NFS mounted file
systems should be set up so that file names are consistant from
machine to machine.) (Be warned that /tmp is usually an exception!)

I agree that there really should be a good way of sending a canvas
over the wire efficiently. i.e. you should be able to have a pixrect
as a cps function argument, which shows up in the server as a canvas,
akin to the way readcanvas works.

	-Don