Re: saned misbehaves with sane_cancel?

David Mosberger-Tang (David.Mosberger@acm.org)
Mon, 27 Jul 1998 23:10:41 -0700

>>>>> On Fri, 24 Jul 1998 03:34:55 -0400 (EDT), Matto Marjanovic <maddog@mir.com> said:

Matto> Now that the microtek backend should properly handle
Matto> sane_cancel, I've been cancelling scans left and right....

Matto> It seems that when 'saned' processes a cancel request, it
Matto> immediately closes the connection back to the net backend.
Matto> This leaves the frontend (and net backend) confused and
Matto> stalled.

Yup, I can reproduce this with xscanimage & the Mustek backend.

Matto> I don't see why it should close the connection at all -- it's
Matto> still valid for the frontend to ask for a new scan, change
Matto> options, etc., after a scan is KO'ed.

Correct. A "cancel" does close the _data_ connection, but the control
connection should remain open. Off-hand, I'm not sure what's going
wrong.

--david

--
Source code, list archive, and docs: http://www.mostang.com/sane/
To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com