All of lore.kernel.org
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmail.com>
To: Tim Waugh <twaugh@redhat.com>,
	Open Printing <printing-architecture@lists.linux-foundation.org>
Subject: Re: [Printing-architecture] cups-browsed: how to treat rejecting queues?
Date: Mon, 04 Nov 2013 14:21:16 +0100	[thread overview]
Message-ID: <52779F4C.5070909@gmail.com> (raw)
In-Reply-To: <1383567790.3894.4.camel@rubik>

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.
> */
> 


  reply	other threads:[~2013-11-04 13:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-04 12:23 [Printing-architecture] cups-browsed: how to treat rejecting queues? Tim Waugh
2013-11-04 13:21 ` Till Kamppeter [this message]
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

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=52779F4C.5070909@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.