Posted May 22, 2012 16:11 UTC (Tue) by randomguy3 (subscriber, #71063)
Parent article: Announcing printerd
I'm guessing that the purpose of this is to be a "super-lightweight cups" for the common case where you want to print (a) infrequently and (b) to a fairly standard page printer (ie: not a receipt printer or anything). Running over D-Bus means it can be asynchronous and started on-demand, so avoiding using resources when not needed.
It will presumably be able to talk to IPP servers (via the relevant cups driver?), which might either run on the local machine (if you sometimes have more demanding requirements, like receipt printing) or on a remote machine (particularly in businesses, for example).
The issue, of course, is the transition period, where everyone will have to support everything. The announcement suggests that there will be a lightweight IPP server available at some point, which could be used to support CUPS-only applications (but negates the on-demand part of printerd), but applications using printerd's D-Bus interface will also have to support cups (or one of its compatibility modes, like lpr) directly to work on systems that don't have printerd.