X Version 11
Release 6.4
Protocols
5
Errors: XPBadContext, XPBadSequence
This request causes the print job associated with the current print context to end. If cancel is FALSE, any
accumulated print data that remains is either sent to the printer or made available to PrintGetDocument-
Data
.
The request generates an XPPrintNotify event with its detail field set to XPEndJobNotify.
When cancel is TRUE, the job currently being processed is canceled. The server may discard any pending
output or may produce partial output. If the job was started in XPGetData mode, then the entire data output
stream is implementation-defined.
If PrintEndJob is called immediately after PrintEndPage, then a synthetic PrintEndDoc is generated by
print server before PrintEndJob. The pool of XPJobAttr attributes that was frozen when the PrintStart-
Job
request was executed is released when PrintEndJob is called.
PrintGetDocumentData
context: PCONTEXT
max-bytes: CARD32
+
status-code: {XPGetDocFinished, XPGetDocSecondConsumer, XPGetDocError}
finished-flag: CARD32
data: LISTofBYTE
Errors: XPBadContext, XPBadSequence, Value
This request returns data generated on a context by other clients.
PrintGetDocumentData
should be sent only after a PrintStartJob request with save_data set to XPGet-
Data
has been executed.
PrintGetDocumentData
generates multiple replies. Each reply is no larger than the value specified in max-
bytes. The final reply is generated by PrintEndJob and has finished-flag set to TRUE.
If the value for max-bytes is zero, a Value error is generated.
An XPBadSequence error is generated if PrintGetDocumentData is executed before PrintStartJob or if
PrintGetDocumentData
is executed after PrintStartJob with save_data set to XPSpool.
PrintPutDocumentData
drawable: DRAWABLE
data: LISTofBYTE
doc-format, options: STRING8
Errors: XPBadContext, XPBadSequence, Match, Value, Drawable