All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Meixner <jsmeix@suse.de>
To: printing-architecture@lists.linux-foundation.org
Subject: [Printing-architecture] Will IPP printer devices and Printer Applications obsolete the cupsd?
Date: Fri, 14 Aug 2020 10:47:42 +0200	[thread overview]
Message-ID: <b632639fbe44c484b718bfb5ff5c8f57@suse.de> (raw)


Hello,

I have a general question:

Will IPP printer devices and Printer Applications obsolete the cupsd?

My current understanding about future Linux printing is that
"printing targets" (i.e. whereto clients send what to print)
will be only IPP servers
either as IPP server running inside an IPP printer device
or as IPP server running in a Printer Application
and
clients autodetect the "printing targets" via DNS-SD
(mostly indirectly via a DNS-SD listener like Avahi)
and then
clients communicate via IPP directly with a "printing target"
to get the actual printing done.

The cupsd is also an IPP server
but when clients communicate directly with
IPP printer devices or Printer Applications
I wonder what is left as use case to have a cupsd running?

Or in other words:
When filters and backends are dropped from CUPS
what would be still left to do for a cupsd?
I.e. what service would a cupsd still provide then?
Cf.
https://www.cups.org/doc/man-filter.html
and
https://www.cups.org/doc/man-backend.html
that read (excerpt)
"CUPS printer drivers and backends are deprecated and
will no longer be supported in a future feature release of CUPS"


Kind Regards
Johannes Meixner
-- 
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5 - 90409 Nuernberg - Germany
(HRB 36809, AG Nuernberg) GF: Felix Imendoerffer


             reply	other threads:[~2020-08-14  8:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-14  8:47 Johannes Meixner [this message]
2020-08-14  9:57 ` [Printing-architecture] Will IPP printer devices and Printer Applications obsolete the cupsd? Till Kamppeter
2020-08-14 11:45   ` Johannes Meixner
2020-08-14 14:29     ` Michael Sweet
2020-08-14 14:25 ` 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=b632639fbe44c484b718bfb5ff5c8f57@suse.de \
    --to=jsmeix@suse.de \
    --cc=printing-architecture@lists.linux-foundation.org \
    /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.