I agree. In fact, we may want to suggest that clients SHOULD
be listening to the port while sending the body of the request.
This would be usefull if the job gets canceled while transmitting
the body, say by an administrator. If the printer implementation
quits pulling data off of the network and sends the response, the
client may appear to be 'hung' until all the data is sent. In
fact, this was the behavior I noticed from some clients I saw at
the Bake Off. The cleanest way to handle this is for the printer
implementation to send a reply that the job was canceled (through
job-status?) and then let the client close down the connection.
If the client does not close down the connection then the server
should time out and reset the connection. If this happens then
the client may loose the response from the server. Thoughts
anyone?
regards,
Brian
--
=============================================================
Brian R. Glass Tektronix, Inc
26600 SW Parkway
Color Printing & Imaging Division PO Box 1000
MS 60-368
mailto:Brian.Glass@tek.com Wilsonville, OR 97070-1000
http://www.tek.com/Color_Printers (503) 685-2456
=============================================================