From: Till Kamppeter <till.kamppeter@gmail.com>
To: Michael Sweet <msweet@apple.com>
Cc: Open Printing <printing-architecture@lists.linux-foundation.org>,
Marek Kasik <mkasik@redhat.com>
Subject: Re: [Printing-architecture] Some suggestions for the DNS-SD (Bonjour) printer support in the dialog
Date: Thu, 13 Jun 2013 16:34:45 +0200 [thread overview]
Message-ID: <51B9D885.8040304@gmail.com> (raw)
In-Reply-To: <D58FE099-79EB-4E3D-904F-B09F4D787B89@apple.com>
On 06/13/2013 01:25 PM, Michael Sweet wrote:
> One of the things I'll be working on post-1.7 is a generic IPP service API that can be used to implement custom spoolers, lightweight print services on NAS boxes, etc. The same API could be used as the basis of a user session print service that interfaces directly with IPP printers and talks to a local cupsd for USB and other legacy queues, or to (for example) implement a service on top of, say, Gutenprint to provide an IPP Everywhere gateway to raster drivers (one possible post-PPD future).
>
> The key is re-use of the core CUPS bits (we've already had a lot of success with that at Apple) and abstracting away the common service/spooler aspects so that the only maintenance you have is for the small bits of glue code you use.
This is a great idea which was really missing, having the daemon's
functionality in a library and letting the developer costumize a
printing system concept as needed. In which time frame will this be
done? 1.8? Summer 2014?
Till
next prev parent reply other threads:[~2013-06-13 14:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 19:48 [Printing-architecture] Some suggestions for the DNS-SD (Bonjour) printer support in the dialog Till Kamppeter
2013-05-17 5:32 ` Michael Sweet
2013-05-17 7:21 ` Till Kamppeter
2013-05-17 14:17 ` Michael Sweet
2013-05-18 23:45 ` James Cloos
2013-05-19 6:08 ` Michael Sweet
2013-06-12 22:52 ` Till Kamppeter
2013-06-13 14:05 ` Michael Sweet
2013-05-17 10:02 ` Tim Waugh
2013-05-17 14:20 ` Michael Sweet
2013-06-13 10:01 ` Till Kamppeter
2013-06-13 11:25 ` Michael Sweet
2013-06-13 14:34 ` Till Kamppeter [this message]
2013-06-13 14:40 ` Michael Sweet
2013-06-13 11:42 ` Tim Waugh
2013-06-13 12:20 ` Till Kamppeter
2013-06-13 14:08 ` Michael Sweet
[not found] ` <51962BA7.4030304@redhat.com>
2013-05-17 14:23 ` Michael Sweet
2013-05-17 18:14 ` Till Kamppeter
[not found] ` <D36BAB03-9A91-42E9-A994-DC0D3C6C254D@apple.com>
2013-06-13 10:11 ` Till Kamppeter
2013-06-13 11:39 ` Michael Sweet
2013-06-13 12:49 ` Till Kamppeter
2013-06-13 14:19 ` Michael Sweet
2013-06-13 9:58 ` Till Kamppeter
2013-06-13 11:18 ` 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=51B9D885.8040304@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=mkasik@redhat.com \
--cc=msweet@apple.com \
--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.