From: Michael Sweet <mike@easysw.com>
To: Pete Zannucci <pzaan@us.ibm.com>
Cc: printing-architecture@freestandards.org
Subject: Re: [Printing-architecture] Bi-di plug-in functionarities
Date: Fri, 06 Dec 2002 13:11:32 -0500 [thread overview]
Message-ID: <3DF0E854.3050802@easysw.com> (raw)
In-Reply-To: <OF69D15E56.869D8C9E-ON85256C87.0057F781@pok.ibm.com>
Pete Zannucci wrote:
> 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?
The backend would have to understand the PDL, which is one of the
reasons we've added backchannel support in CUPS 1.2 so that the
driver (which is generating the PDL) can handle these details.
> 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?
There isn't any reason that you couldn't create a backend that
communicated with a common interface/daemon/server to provide
concurrent access to a device; the HP OfficeJet drivers do this
IIRC...
The main issue is that print data is generated by the filters
for the whole job as a stream, so drivers/backends need to save
the whole print file if they want to support recovery. Also,
you may need to add a common set of initialization commands
to the front of any recovery data to get the printer into the
right mode(s).
What we're concentrating on for CUPS 1.2 is better error tracking,
page accounting, and event notification which will allow for more
robust drivers to be written.
--
______________________________________________________________________
Michael Sweet, Easy Software Products mike@easysw.com
Printing Software for UNIX http://www.easysw.com
next prev parent reply other threads:[~2002-12-06 18:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-06 16:10 [Printing-architecture] Bi-di plug-in functionarities Pete Zannucci
2002-12-06 18:11 ` Michael Sweet [this message]
2002-12-09 10:01 ` Yasumasa TORATANI
2002-12-09 14:19 ` Michael Sweet
2002-12-10 10:52 ` Yasumasa TORATANI
2002-12-10 15:30 ` Michael Sweet
2002-12-12 13:49 ` Yasumasa TORATANI
-- strict thread matches above, loose matches on Subject: below --
2002-12-10 15:18 Pete Zannucci
2002-12-12 13:53 ` Yasumasa TORATANI
2002-12-09 16:44 Pete Zannucci
2002-12-09 20:49 ` Michael Sweet
2002-12-06 13:04 Yasumasa TORATANI
2002-12-06 15:38 ` Michael Sweet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3DF0E854.3050802@easysw.com \
--to=mike@easysw.com \
--cc=printing-architecture@freestandards.org \
--cc=pzaan@us.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.