Re: [Printing-architecture] CUPS 3.x: Printing via D-Bus

On 27/04/2022 14:21, Michael Sweet wrote:
> Till,
> 
> My thoughts on the DBUS interface (and any future XPC interface, should Apple adopt our work) is that it should expose the same IPP operations, attributes, and values as are available over HTTP.
> 
> The local spooler needs to:
> 
> 1. Manage a dynamic list of print destinations (DNS-SD, mDNS, local configuration profiles, Printer Applications, etc.)
> 2. Do queries for state/configuration/capabilities for a given destination, with some level of caching
> 3. Manage a dynamic list of queued jobs for those destinations, with the usual Create/Cancel/Reprint-Job functionality
> 4. Do minimal conversion/transform of document data for the destination (text, image, and PDF to PDF/raster)
> 5. Report any printer/job errors with possible actions (cancel, retry, etc.)
> 6. Handle any authentication challenges when sending jobs to destinations
> 

So the D-Bus interface should be some kind of IPP-over-D-Bus, supporting 
not only the few operations a print dialog needs to do, but instead, 
support all operations one needs for the local CUPS server?

Then it is well differnt to CPDB and trying to make one out of both will 
not actually work. So I will continue CPDB as it was before.

    Till