[cups.general] [patch] IPP_PORT setting
Michael Sweet
mike at easysw.com
Fri Aug 13 14:15:19 PDT 2004
Colin Walters wrote:
> 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.
Can you post this patch to the STR form at:
http://www.cups.org/str.php
That way we can track it, it won't get lost, etc. :)
Thanks!
>> 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.
> ...
That's what the CUPS_SERVER and IPP_PORT environment variables are
for... :) The side-effect for the IPP backend is fairly unique, I
think.
--
______________________________________________________________________
Michael Sweet, Easy Software Products mike at easysw dot com
Printing Software for UNIX http://www.easysw.com
More information about the cups
mailing list