AW: [Desktop_printing] Role of CUPS and error handling

Norm Jacobs Norm.Jacobs at Sun.COM
Fri Mar 24 11:58:02 PST 2006


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.

       -Norm




More information about the Printing-summit mailing list