All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zdenek Dohnal <zdohnal@redhat.com>
To: "printing-architecture@lists.linux-foundation.org"
	<printing-architecture@lists.linux-foundation.org>,
	ipp@pwg.org
Cc: bugzilla@countrybusdevon.co.uk
Subject: [Printing-architecture] How to send a job to printer's internal memory to have it available for reprinting via IPP
Date: Fri, 29 Jul 2022 10:08:46 +0200	[thread overview]
Message-ID: <7690e8a3-6bf6-cb69-03d6-e8e8328df373@redhat.com> (raw)

Hi all,

I have a user (Neil in CC) in Fedora (see comment 
https://bugzilla.redhat.com/show_bug.cgi?id=2095755#c22 ) who has a 
Kyocera printer, which is capable of driverless printing, however he 
sticks with classic driver, because it can save the print job data 
directly into the printer's memory, and user can reprint the job 
directly on the printer (he doesn't want to reprint from CUPS interface 
on PC).

Is something similar doable via driverless printing over IPP 2.0+ via 
CUPS? Or is there a standard defining such functionality?

I can imagine a similar behavior with IPP can be achieved if the printer 
has a job log and saves the job files for some time (just as cupsd 
does), and provides a button in menu or somewhere which will reprint the 
job - but this whole would have to be implemented in printer's firmware...

Thank you in advance!


Zdenek

-- 
Zdenek Dohnal
Software Engineer
Red Hat, BRQ-TPBC


             reply	other threads:[~2022-07-29  8:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-29  8:08 Zdenek Dohnal [this message]
2022-07-29 12:12 ` [Printing-architecture] [IPP] How to send a job to printer's internal memory to have it available for reprinting via IPP 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=7690e8a3-6bf6-cb69-03d6-e8e8328df373@redhat.com \
    --to=zdohnal@redhat.com \
    --cc=bugzilla@countrybusdevon.co.uk \
    --cc=ipp@pwg.org \
    --cc=printing-architecture@lists.linux-foundation.org \
    /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.