* [Printing-architecture] cups-browsed: how to treat rejecting queues?
@ 2013-11-04 12:23 Tim Waugh
2013-11-04 13:21 ` Till Kamppeter
2013-11-04 15:09 ` Till Kamppeter
0 siblings, 2 replies; 6+ messages in thread
From: Tim Waugh @ 2013-11-04 12:23 UTC (permalink / raw)
To: Open Printing; +Cc: Till Kamppeter
[-- Attachment #1: Type: text/plain, Size: 564 bytes --]
When cups-browsed creates local queues to forward jobs to remote queues,
I wonder how it should treat queues that are not accepting jobs? The way
cupsd used to behave was to copy the remote printer's state to the local
implicit queue, but cups-browsed is not structured in that way: it
doesn't update the queues it creates.
The problem with the current behaviour is that the GTK+ print dialog
will allow a queue rejecting jobs to be selected.
See also discussion of this for Fedora:
https://bugzilla.redhat.com/show_bug.cgi?id=1025263
Tim.
*/
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 482 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Printing-architecture] cups-browsed: how to treat rejecting queues?
2013-11-04 12:23 [Printing-architecture] cups-browsed: how to treat rejecting queues? Tim Waugh
@ 2013-11-04 13:21 ` Till Kamppeter
2013-11-08 18:01 ` Tim Waugh
2013-11-04 15:09 ` Till Kamppeter
1 sibling, 1 reply; 6+ messages in thread
From: Till Kamppeter @ 2013-11-04 13:21 UTC (permalink / raw)
To: Tim Waugh, Open Printing
Tim, one can solve the problem, cups-browsed updates queues on changes
in the Bonjour record from the server (but not sure whether on all
changes). Rejecting jobs is encoded in the printer-type TXT field, by
the 0x80000 bit. See /usr/include/cups/cups.h, CUPS_PRINTER_REJECTING
constant.
So it should be possible to implement that the cups-browsed queue
follows the accepting bit of its remote queue.
Till
On 11/04/2013 01:23 PM, Tim Waugh wrote:
> When cups-browsed creates local queues to forward jobs to remote queues,
> I wonder how it should treat queues that are not accepting jobs? The way
> cupsd used to behave was to copy the remote printer's state to the local
> implicit queue, but cups-browsed is not structured in that way: it
> doesn't update the queues it creates.
>
> The problem with the current behaviour is that the GTK+ print dialog
> will allow a queue rejecting jobs to be selected.
>
> See also discussion of this for Fedora:
> https://bugzilla.redhat.com/show_bug.cgi?id=1025263
>
> Tim.
> */
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Printing-architecture] cups-browsed: how to treat rejecting queues?
2013-11-04 12:23 [Printing-architecture] cups-browsed: how to treat rejecting queues? Tim Waugh
2013-11-04 13:21 ` Till Kamppeter
@ 2013-11-04 15:09 ` Till Kamppeter
2013-11-04 16:08 ` Michael Sweet
1 sibling, 1 reply; 6+ messages in thread
From: Till Kamppeter @ 2013-11-04 15:09 UTC (permalink / raw)
To: Tim Waugh, Open Printing
On 11/04/2013 01:23 PM, Tim Waugh wrote:
> When cups-browsed creates local queues to forward jobs to remote queues,
> I wonder how it should treat queues that are not accepting jobs? The way
> cupsd used to behave was to copy the remote printer's state to the local
> implicit queue, but cups-browsed is not structured in that way: it
> doesn't update the queues it creates.
>
> The problem with the current behaviour is that the GTK+ print dialog
> will allow a queue rejecting jobs to be selected.
>
> See also discussion of this for Fedora:
> https://bugzilla.redhat.com/show_bug.cgi?id=1025263
>
> Tim.
> */
>
I have checked further, cups-browsed indeed does not update queues on
Bonjour record changes, the update to https is triggered by a completely
new Bonjour broadcast.
I have also tried to switch a printer on my server between accepting and
rejecting state, and this does not make CUPS/Avahi generating an update
of the Bonjour record (= sending a broadcast), avahi-discover on a
client did not show any evidence of a signal broadcasted because of this
change. Can this be a bug in CUPS which we should report?
Till
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Printing-architecture] cups-browsed: how to treat rejecting queues?
2013-11-04 15:09 ` Till Kamppeter
@ 2013-11-04 16:08 ` Michael Sweet
2013-11-04 16:18 ` Till Kamppeter
0 siblings, 1 reply; 6+ messages in thread
From: Michael Sweet @ 2013-11-04 16:08 UTC (permalink / raw)
To: Till Kamppeter; +Cc: printing-architecture@lists.linux-foundation.org
Till,
On Nov 4, 2013, at 10:09 AM, Till Kamppeter <till.kamppeter@gmail.com> wrote:
> ...
> I have also tried to switch a printer on my server between accepting and
> rejecting state, and this does not make CUPS/Avahi generating an update
> of the Bonjour record (= sending a broadcast), avahi-discover on a
> client did not show any evidence of a signal broadcasted because of this
> change. Can this be a bug in CUPS which we should report?
This is a conscious design decision for cupsd - we do not re-register the TXT records on simple state changes.
Conceptually we might want to stop sharing a printer that is not accepting jobs. Something to think about…
____________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Printing-architecture] cups-browsed: how to treat rejecting queues?
2013-11-04 16:08 ` Michael Sweet
@ 2013-11-04 16:18 ` Till Kamppeter
0 siblings, 0 replies; 6+ messages in thread
From: Till Kamppeter @ 2013-11-04 16:18 UTC (permalink / raw)
To: Michael Sweet; +Cc: printing-architecture@lists.linux-foundation.org
On 11/04/2013 05:08 PM, Michael Sweet wrote:
> Till,
>
> On Nov 4, 2013, at 10:09 AM, Till Kamppeter <till.kamppeter@gmail.com> wrote:
>> ...
>> I have also tried to switch a printer on my server between accepting and
>> rejecting state, and this does not make CUPS/Avahi generating an update
>> of the Bonjour record (= sending a broadcast), avahi-discover on a
>> client did not show any evidence of a signal broadcasted because of this
>> change. Can this be a bug in CUPS which we should report?
>
> This is a conscious design decision for cupsd - we do not re-register the TXT records on simple state changes.
>
> Conceptually we might want to stop sharing a printer that is not accepting jobs. Something to think about…
Yes, I think this would be a good idea.
Till
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2013-11-08 18:01 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-11-04 12:23 [Printing-architecture] cups-browsed: how to treat rejecting queues? Tim Waugh
2013-11-04 13:21 ` Till Kamppeter
2013-11-08 18:01 ` Tim Waugh
2013-11-04 15:09 ` Till Kamppeter
2013-11-04 16:08 ` Michael Sweet
2013-11-04 16:18 ` Till Kamppeter
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.