[cups.general] socket backend: why not call shutdown immediately?

[Michael Sweet]

On Feb 5, 2010, at 9:08 AM, Tim Waugh wrote:

> On Fri, 2010-02-05 at 08:40 -0800, Michael Sweet wrote:
>> Because some printers break when we do this (more specifically, as
>> soon as we shutdown our side of the connection they decide to do the
>> same with their side instead of sending any remaining back-channel
>> data...)
> 
> Rats, I wondered if that was the case.
> 
>> However, the reasons for keeping this workaround in place (waiting for
>> back-channel data) are going away soon, so maybe in CUPS 1.5 (at
>> least) we can just remove the extra "wait for back-channel data" code
>> since it isn't needed in the general case - just for drivers or
>> "auto-setup tools" on Mac OS X that close their stdout pipe when they
>> are done sending data but not done reading a response.
>> 
>> Care to file a bug?
> 
> Sure.
> 
> In the mean time, how about if we added a 'waitbc' option to the socket
> backend, defaulting to on (the current behaviour), but with 'off'
> meaning not to wait?

I hate to add an option that will disappear in the next release.  Since I'm only aware of issues with Mac OS X drivers needing the extra backchannel wait time, how about we just wrap it in "#ifdef __APPLE__" for 1.4 and remove it in 1.5?

___________________________________________________
Michael Sweet, Senior Printing System Engineer