From: Till Kamppeter <till.kamppeter@gmail.com>
To: Michael Sweet <msweet@apple.com>, James Cloos <cloos@jhcloos.com>
Cc: "printing-architecture@lists.linux-foundation.org"
<printing-architecture@lists.linux-foundation.org>,
Jeff Licquia <jeff@licquia.org>
Subject: Re: [Printing-architecture] How to add IPP over USB printer support to Linux?
Date: Mon, 24 Feb 2014 18:53:08 +0100 [thread overview]
Message-ID: <530B8704.2010608@gmail.com> (raw)
In-Reply-To: <9576314E-B688-420E-825D-523F6ABFB7D3@apple.com>
On 02/24/2014 01:54 PM, Michael Sweet wrote:
> James,
>
> Putting it in the USB backend would greatly increase the complexity of that backend without actually enabling things like the embedded web interface of the printer and other IPP and HTTP services offered by these printers over USB. Also, while the IPP API in libcups can handle alternate IO paths, the HTTP API is tied to sockets, so any implementation inside the USB backend would need to provide its own mini HTTP API to send requests and receive responses over USB.
>
> On OS X we have a launchd service (launch-on-demand) that is setup when a printer is connected and removed when disconnected. This service basically acts as a proxy or gateway between IP connections and the USB interfaces offered by the printer (minimum requirement is 2 interfaces, which looks to be the limit for most printers in the foreseeable future thanks to the SoCs they use...), and the service arbitrates access from multiple IPP/HTTP clients to that limited number of IP interfaces.
>
Is it already possible to buy an IPP-over-USB printer? If yes, which
model(s)? Would be great if one could by one for an appropriate Linux
kernel developer.
Till
next prev parent reply other threads:[~2014-02-24 17:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 18:52 [Printing-architecture] How to add IPP over USB printer support to Linux? Ira McDonald
2014-02-22 7:12 ` James Cloos
2014-02-24 12:54 ` Michael Sweet
2014-02-24 17:53 ` Till Kamppeter [this message]
2014-02-24 18:16 ` Michael Sweet
2014-02-25 22:37 ` James Cloos
2014-02-26 1:27 ` 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=530B8704.2010608@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=cloos@jhcloos.com \
--cc=jeff@licquia.org \
--cc=msweet@apple.com \
--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.