[Omniprint-developer] Re: [Inkjet-list] Re: Taking a step back

[Michael S. <mi...@ea...>]

On Friday 28 December 2001 11:01 am, Robert L Krawitz wrote:
> ...
> That would probably work, although applications would need to reread
> the PPD whenever they wanted to start a new print job.

I think this would be the case, even for a dynamic data interface.

>                                                          For that
> matter, so would CUPS.

Yes, but the device daemons that are being used do this by telling
CUPS to use the new PPD file (i.e. CUPS only re-reads the file as
needed)

> ...
>    Well, for CUPS-based drivers at least it will work, and other apps
>    will "see" the standard PPD file that will still work everywhere.
>
> I'm nervous about what this leads to.  If CUPS has one set of
> extensions, another IPP-based system has another, and so forth, we
> get into trouble fast.

Not to "toot our own horn" too much, but right now CUPS is the only
IPP implementation that actually deals with printer drivers, options,
etc. at this level.  MS IPP and Novell IPP both still deal just with
sending raw print data... :(  Also, CUPS is already extending IPP
by providing PPD files, drivers, etc. on top of IPP (documented and
registered, of course, with the PWG), and anything we do to support
printer drivers on top of IPP will be an extension...

-- 
______________________________________________________________________
Michael Sweet, Easy Software Products                  mi...@ea...
Printing Software for UNIX                       http://www.easysw.com