From: Tim Waugh <twaugh@redhat.com>
To: Till Kamppeter <till.kamppeter@gmail.com>
Cc: Open Printing <printing-architecture@lists.linux-foundation.org>
Subject: Re: [Printing-architecture] Removal of features in CUPS
Date: Thu, 12 Jan 2012 10:51:15 +0000 [thread overview]
Message-ID: <1326365475.8483.3.camel@worm.elk> (raw)
In-Reply-To: <4F0E23F2.5010608@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 523 bytes --]
Hi Till,
I think that CUPS Browsing is also being removed in 1.6, leaving Avahi
as the sanest of the remaining discovery methods.
The current state of the Avahi support patches is that service
announcement is working in the scheduler, and service discovery is
working in the dnssd backend -- i.e. by manual user intervention.
What is currently missing is automatic service discovery in the
scheduler, so that shared queues can be discovered by CUPS itself as
used to happen with CUPS Browsing.
Tim.
*/
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 482 bytes --]
next prev parent reply other threads:[~2012-01-12 10:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 0:06 [Printing-architecture] Removal of features in CUPS Till Kamppeter
2012-01-12 10:51 ` Tim Waugh [this message]
2012-01-12 11:09 ` Till Kamppeter
2012-01-12 11:56 ` Tim Waugh
-- strict thread matches above, loose matches on Subject: below --
2012-02-03 16:32 Michael Sweet
2012-02-03 17:09 ` Michael Sweet
2012-02-07 18:07 ` Till Kamppeter
2012-02-08 16:19 ` Michael Sweet
2012-02-08 21:58 ` Till Kamppeter
2012-02-09 2: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=1326365475.8483.3.camel@worm.elk \
--to=twaugh@redhat.com \
--cc=printing-architecture@lists.linux-foundation.org \
--cc=till.kamppeter@gmail.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.