AW: [Desktop_printing] Role of CUPS and error handling
Michael Sweet
mike at easysw.com
Fri Mar 24 12:14:32 PST 2006
Norm Jacobs wrote:
> Michael Sweet wrote:
>
>>
>> They can also run CUPS on an alternate port like 8631 - it'll kill
>> interoperability, but then they can run cupsd by default.
>>
> While I agree that it isn't preferable to run an IPP service (CUPS) at some
> port other than 631, It shouldn't break interoperability. The PAPI, CUPS,
> and Windows implementations of client side support will all let you direct
> your IPP connection to whichever port your like. I woudl be surprised if
> that weren't true of other implementations.
> ipp://server:8631/printers/queue
> http://server:8631/printers/queue
>
> The fact is, I have a system with Solaris LP listening on 631 and
> CUPS listening on a different port for PAPI/IPP testing and results
> comparison.
Yes, and I do that here to test new versions of CUPS while a stable
install is running on 631.
When I say interoperability, I mean having a network full of CUPS
systems, some using the standard 631 and others using the new non-
privileged port. CUPS clients will not automatically see the
servers on the other ports, as they will only be listening to their
own default port.
--
______________________________________________________________________
Michael Sweet, Easy Software Products mike at easysw dot com
Internet Printing and Document Software http://www.easysw.com
More information about the Printing-summit
mailing list