From: Till Kamppeter <till.kamppeter@gmail.com>
To: Tim Waugh <twaugh@redhat.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 14:20:42 +0200 [thread overview]
Message-ID: <51B9B91A.6010609@gmail.com> (raw)
In-Reply-To: <1371123741.31435.2.camel@rubik>
On 06/13/2013 01:42 PM, Tim Waugh wrote:
> On Thu, 2013-06-13 at 12:01 +0200, Till Kamppeter wrote:
>> This would mean to resemble large parts of CUPS (spooling, filtering,
>> but not networking) for a per-user/per-app printing system
>
> My idea (printservice) for this was:
> 1. Avoid spooling altogether, just send job direct to network queue
> (this is often another spooler in any case)
Should be the case for laser printers with built-in network connection,
I don't know how it is with inkjets. Or does IPP Everywhere also require
spooling space inside the printer?
> 2. Avoid most filtering by requiring jobs to be application/pdf and
> requiring that allowable network queues support application/pdf.
>
As IPP Everywhere has only PWG Raster as required format (the others are
optional), we need at least a pdftoraster filter, but this one filter is
already much better than having device-specific drivers and data fo
1000s of printers.
Till
next prev parent reply other threads:[~2013-06-13 12:20 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
2013-06-13 14:40 ` Michael Sweet
2013-06-13 11:42 ` Tim Waugh
2013-06-13 12:20 ` Till Kamppeter [this message]
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=51B9B91A.6010609@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=mkasik@redhat.com \
--cc=printing-architecture@lists.linux-foundation.org \
--cc=twaugh@redhat.com \
/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.