Why is ipp mandatory as protocol for browsedprinters?

Christer Bernérus bernerus at chalmers.se
Fri Aug 27 07:04:26 PDT 2010


> On Aug 26, 2010, at 10:52 AM, Christer Bern=C3=A9rus wrote:
> > The browse protocol states that the uri must begin with ipp://, and =
> cupsd enforces this. As cups is built, there is a one-to-one =
> relationship between the protocol part of the uri and the cups backend. =
> This means that there is no way to use a custom built cups backend to =
> accept browse packets.
> >=20
> > Why is there such a limit ?

OK, Thanks Mike. That seems like a good reason.

>
> CUPS browsing allow a client to discover printers that can be used with =
> 0 configuration or extra software on the client side. Allowing protocols =
> and printers that do not work this way would break that "semantic =
> contract" and lead to a lot of user frustration.
>
> Discovery for other protocols is handled by the backends themselves and, =
> in some circumstances, by "helper" backends like dnssd and snmp that do =
> discovery and advertise queues for other protocols.
>
> ________________________________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
>
>
>
>





More information about the cups-devel mailing list