From: Till Kamppeter <till.kamppeter@gmail.com>
To: Tim Waugh <twaugh@redhat.com>
Cc: Open Printing <printing-architecture@lists.linux-foundation.org>
Subject: Re: [Printing-architecture] Removal of features in CUPS
Date: Thu, 12 Jan 2012 12:09:44 +0100 [thread overview]
Message-ID: <4F0EBF78.1020805@gmail.com> (raw)
In-Reply-To: <1326365475.8483.3.camel@worm.elk>
On 01/12/2012 11:51 AM, Tim Waugh wrote:
> 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.
Does libdnssd-based upstream CUPS do automatic service discovery by the
scheduler, meaning that your Avahi patch is not yet complete in this
sense or is automatic service discovery by the scheduler even not
implemented at all upstream, meaning that by removing IPP browsing one
of the most important features of CUPS gets lost?
Till
next prev parent reply other threads:[~2012-01-12 11:09 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
2012-01-12 11:09 ` Till Kamppeter [this message]
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=4F0EBF78.1020805@gmail.com \
--to=till.kamppeter@gmail.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.