File Transmission
Upgrade Spruce to use extended EFTP protocol, as defined in recent Taft memoranda. When Sprint is running, respond with "wait a while".
Break Page Information
Printed by
Created by
Printing Controls
Include in all protocols capability for unique identifier for file to be supplied by client or server, used in subsequent communication re: file.
Early: include password in protocol; optional if file is to be printed right away, mandatory if accompanied by "hold for arrival". Server implements decision whether to allow reprint of documents not accompanied by password; if password supplied, it must be entered at server to enable reprint, etc.Later: use authentication servers, at least optionally, to avoid cleartext transmission of passwords.
Hold for arrival: mandatory password, file is marked "printed" or otherwise queued, with timeout, for printing later. When user arrives at server and types password, file gets high priority.
Reprint or "Print now" command by network command? Similar password requirements. Might be combined with capability spooling, below.
# copies to print, page range to print -- allowed in commands accompanying file, in capability-style requests (below), or in reprint command (above).
Font Information
Font transmission to printer -- temporary and/or permanent? Bit maps at known printer resolution, as well as perhaps splines and other things.
Capability Spooling
Early: Send file name to printer, along with other print instance information. Later: change file name to capability for file. Printer uses whatever protocol, but probably FTP, to get the file.
Document-wide, page-wide complexity information
Colors used in document; colors used page by page.
Overlapping objects do/do not appear in document, on individual pages (allows more efficient version of microcode if not.)
"EARS" protocol extensions
Report on individual files
Extended report on state of system, including jam/low supplies reporting, load, backlog, scheduled down time, etc.
Report of name, type, version, capabilities, of responding printer, in machine-processable form.
Use of other printers, or other kinds of servers, to provide information about "down" printers.
Use of registration servers, etc., to identify printers and their capabilities.