[Printing-architecture] Bi-di plug-in functionarities

Pete Zannucci pzaan at us.ibm.com
Fri Dec 6 08:10:32 PST 2002

Michael Sweet wrote:

> 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.

With using backends, how do we handle spool information that may
be needed to do recovery, restart a job, rerender a page, and possibly
manage other asynchronous events that may need to be mananged?

I realize there may be potential security issues but in my diagrams
I attempted to allow for management of the spool system and rendering
along with async. data manipulation.  Is there any easy way with CUPS
to provide similar function so that we don't end up with issues such
as jobs disappearing along with providing robust recovery from errors?

This direction, especially error recovery and job tracking, has been
a hot button with corporate customers in the past and generated into
a much more integrated solution for bi-di support.


Peter Zannucci

IBM Linux Technology Center
Open Source Software Development
Omni Print Project http://sourceforge.net/projects/omniprint
Austin, TX - Tel. 512-838-4687 (t/l 678) pzaan at us.ibm.com

More information about the Printing-architecture mailing list