[Printing-architecture] Bi-di plug-in functionarities
mike at easysw.com
Fri Dec 6 07:38:56 PST 2002
Yasumasa TORATANI wrote:
> 3) Each bi-di plug-in module for each printer vendor has the
> following functionarities;
> a) Handle the vendor dependent protocol to communicate with
> each vendor's printer.
> b) Obtain the printer status, including error, e.g. ink level,
> paper jam, no cartridge, etc.
> c) Obtain the information of the printer options, e.g. sorter,
> stapler, extended memory, etc.
> d) Printer discovery for both local and network.
> e) No UI. to be simple and generic.
> f) In some cases, receive the printing data from the upper system,
> translate it for eachr device or protocol, and send it to the
> appropriate target.
> g) Send the printer information to the upper system.
FWIW, in CUPS #3 is normally handled by the backend (in CUPS 1.1
and earlier) and/or by the driver (in CUPS 1.2), the idea being
that the same commands/protocols will generally be used over
serial, parallel, USB, and network connections, and since the
driver has a copy of the device URI (the device for the printer)
it can tailor its input/output accordingly.
Michael Sweet, Easy Software Products mike at easysw.com
Printing Software for UNIX http://www.easysw.com
More information about the Printing-architecture