From: Solomon P. <pi...@sh...> - 2019-09-28 12:46:34
|
On Fri, Sep 27, 2019 at 10:50:21PM -0400, Robert Krawitz wrote: > BTW, quite aside from PPD files, there are other advantages to being > an IPP server. Think about the possibility of a containerized > Gutenprint that we really could continuously release every time we add > a new printer (and it passes a somewhat more robust set of tests than > we currently use, of course). Oh, there are significant advantagaes to moving to a fully-vertically-integrated IPP approach -- as well as the release model you describe, under the hood we gain a saner job/page model, option lists that can be dependent on the printer's runtime configuration, far richer status reporting, and more usable mechanisms for accessing "bonus" functionality. But the migration path from where we are now is not so much a path as a near-vertical cliff face. :) Still, I've been slowly working towards this goal with the dyesub family, with the backends seeing a lot of structual rework so that they can operate in both the loosely-coupled legacy CUPS model as well as (what I think) is necessary for a tightly-coupled, always-on IPP printing application. Baby steps.. - Solomon -- Solomon Peachy pizza at shaftnet dot org High Springs, FL ^^ (email/xmpp) ^^ Quidquid latine dictum sit, altum videtur. |