Bug#704238: Need to document the CUPS client's new server-version option
Vincent,
On 2013-06-06, at 7:15 AM, Vincent Lefevre <vincent@vinc17.net> wrote:
>> ...
>> Opinions ?
>
> Agreed, though detecting the IPP version would be much better
> (isn't the negotiation part of the protocol?).
Not really. There is some support for detecting supported versions and reporting when a version is not supported, but that requires clients to re-submit using the supported version. Relatively easy for us to do for the cupsDo*Request APIs, but cupsSendRequest/GetResponse depend on the application to duplicate the logic. There are just too many places to change (even in the CUPS sources) and then we'll still end up getting someone that reports it doesn't work because RandomApplication didn't update their code as well.
Given that this is only a problem for users depending on the ServerName directive in client.conf, it seemed much more practical (and reliable) to have the user/administrator specify any version limitations there.
_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair
Reply to: