On Tue, Sep 6, 2011 at 1:55 PM, Alan Mackenzie <a...@muc.de> wrote: > Hi, Michael. > On Tue, Sep 06, 2011 at 01:02:59PM -0400, Michael Mol wrote: >> On Tue, Sep 6, 2011 at 12:49 PM, Alan Mackenzie <a...@muc.de> wrote: >> It could be that IPP is just becoming the preferred protocol, and other >> print queue managing protocols are going the way of Gopher. > > Preferred by whom? Firefox, for example, manages lprng just fine. It's > really not a big deal supporting an extra spooler interface, particularly > a simple one.
"IPP is just becoming" indicates a change. Where's change coming from? Demand to satisfy new users. Who are the new users? Probably the people running turnkey installs of Ubuntu. For me, IPP and CUPS have "just worked" beautifully*. Any SKU of Windows 7 higher than 'starter' will talk to a CUPS daemon just fine, and will automatically see a CUPS daemon running on the network if the daemon is using running mdns-sd. The one trouble I've had is getting those mdns-sd broadcasts forwarded across my subnets. Change happens. > >> Is there a simple IPP daemon which could wrap lprng? > > Adding a layer of complexity to a daemon to cope with added complexity in > a client program? I doubt it. It sounds like madness. Isn't that what inetd does? nc? Hell, isn't that what "does one thing, and one thing only" KISS philosophy behind unixy commands and piping philosophy has been about all along? Insert a shim or adapter between two things which are related, but not quite compatible? * And, yes, I realize that, for some, it doesn't. That's what mailing lists like this are helpful for...troubleshooting. -- :wq
