[cups.general] [patch] IPP_PORT setting

[Colin Walters]

On Tue, 2004-08-10 at 08:44 -0400, Michael Sweet wrote:

> I would say we probably want to use ippSetPort(IPP_PORT) in the
> IPP backend instead; that will get the behavior you desire without
> impacting the filters. 

Ok, updated patch attached then.

>  We could also look at updating httpSeparate()
> to not use the ippPort() value, but that would have a much wider
> scope so I'd want to do a full audit to see what programs are
> using the port value from it...

Hmm.  I think maybe a better long term solution would be to explicitly
pass a URI (which would include the port) referring to the scheduler as
an argument to the filters.  That would be a filter API/ABI change
though.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: cups-no-propagate-ipp-port.patch
Type: text/x-patch
Size: 723 bytes
Desc: not available
URL: <https://lists.cups.org/pipermail/cups/attachments/20040813/58d7a59b/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <https://lists.cups.org/pipermail/cups/attachments/20040813/58d7a59b/attachment-0002.bin>