Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!newstop!exodus!bendenweyr!flar
From: flar@bendenweyr.Eng.Sun.COM (Jim Graham)
Newsgroups: comp.windows.x
Subject: Re: OW as a PostScript X server...
Message-ID: <3295@exodus.Eng.Sun.COM>
Date: 21 Nov 90 23:33:49 GMT
References: <9011211347.AA18584@lightning.McRCIM.McGill.EDU>
Sender: news@exodus.Eng.Sun.COM
Reply-To: flar@bendenweyr.Eng.Sun.COM (Jim Graham)
Organization: Sun Microsystems, Inc.
Lines: 24

Why isn't there an extension protocol request which blocks the execution
of additional requests from the extension until the PostScript is finished?

Why is a return packet needed to synchronize the two?

I should be able to execute the following:

Xrequest1
Xrequest2
XDPSrequest
Xrequest3
XDPSsynch
Xrequest4
Xflush()

None of the requests need a reply, so they continue to be buffered until
I execute the Xflush() at the end.  The Xrequest3 ends up executing
asynchronously (let's assume that I knew ahead of time that it would be
independent of the results of the XDPSrequest).  Then the synch holds
up the connection until the PostScript is done.  Finally the Xrequest4
gets executed after the DPS stuff is done.  None of this required a
return packet, all it required was one more protocol request.

					...jim