kopia lustrzana https://gitlab.com/sane-project/website
61 wiersze
2.9 KiB
HTML
61 wiersze
2.9 KiB
HTML
<!-- received="Tue Jul 28 07:34:50 1998 PDT" -->
|
|
<!-- sent="Mon, 27 Jul 1998 23:10:41 -0700" -->
|
|
<!-- name="David Mosberger-Tang" -->
|
|
<!-- email="David.Mosberger@acm.org" -->
|
|
<!-- subject="Re: saned misbehaves with sane_cancel?" -->
|
|
<!-- id="199807280610.XAA05635@panda.mostang.com" -->
|
|
<!-- inreplyto="m0yzcNT-000J3sC@yoo-hoo.ai.mit.edu" -->
|
|
<title>sane-devel: Re: saned misbehaves with sane_cancel?</title>
|
|
<h1>Re: saned misbehaves with sane_cancel?</h1>
|
|
<b>David Mosberger-Tang</b> (<a href="mailto:David.Mosberger@acm.org"><i>David.Mosberger@acm.org</i></a>)<br>
|
|
<i>Mon, 27 Jul 1998 23:10:41 -0700</i>
|
|
<p>
|
|
<ul>
|
|
<li> <b>Messages sorted by:</b> <a href="date.html#163">[ date ]</a><a href="index.html#163">[ thread ]</a><a href="subject.html#163">[ subject ]</a><a href="author.html#163">[ author ]</a>
|
|
<!-- next="start" -->
|
|
<li> <b>Next message:</b> <a href="0164.html">Erik Heim: "Is there a driver for a plustek OpticPro 4800P for sane?"</a>
|
|
<li> <b>Previous message:</b> <a href="0162.html">David Mosberger-Tang: "SANE release 0.74 available"</a>
|
|
<li> <b>In reply to:</b> <a href="0161.html">Matto Marjanovic: "saned misbehaves with sane_cancel?"</a>
|
|
<!-- nextthread="start" -->
|
|
<!-- reply="end" -->
|
|
</ul>
|
|
<!-- body="start" -->
|
|
<i>>>>>> On Fri, 24 Jul 1998 03:34:55 -0400 (EDT), Matto Marjanovic <<a href="mailto:maddog@mir.com">maddog@mir.com</a>> said:</i><br>
|
|
<p>
|
|
Matto> Now that the microtek backend should properly handle<br>
|
|
Matto> sane_cancel, I've been cancelling scans left and right....<br>
|
|
<p>
|
|
Matto> It seems that when 'saned' processes a cancel request, it<br>
|
|
Matto> immediately closes the connection back to the net backend.<br>
|
|
Matto> This leaves the frontend (and net backend) confused and<br>
|
|
Matto> stalled.<br>
|
|
<p>
|
|
Yup, I can reproduce this with xscanimage & the Mustek backend.<br>
|
|
<p>
|
|
Matto> I don't see why it should close the connection at all -- it's<br>
|
|
Matto> still valid for the frontend to ask for a new scan, change<br>
|
|
Matto> options, etc., after a scan is KO'ed.<br>
|
|
<p>
|
|
Correct. A "cancel" does close the _data_ connection, but the control<br>
|
|
connection should remain open. Off-hand, I'm not sure what's going<br>
|
|
wrong.<br>
|
|
<p>
|
|
--david<br>
|
|
<p>
|
|
<p>
|
|
<pre>
|
|
--
|
|
Source code, list archive, and docs: <a href="http://www.mostang.com/sane/">http://www.mostang.com/sane/</a>
|
|
To unsubscribe: echo unsubscribe sane-devel | mail <a href="mailto:majordomo@mostang.com">majordomo@mostang.com</a>
|
|
</pre>
|
|
<!-- body="end" -->
|
|
<p>
|
|
<ul>
|
|
<!-- next="start" -->
|
|
<li> <b>Next message:</b> <a href="0164.html">Erik Heim: "Is there a driver for a plustek OpticPro 4800P for sane?"</a>
|
|
<li> <b>Previous message:</b> <a href="0162.html">David Mosberger-Tang: "SANE release 0.74 available"</a>
|
|
<li> <b>In reply to:</b> <a href="0161.html">Matto Marjanovic: "saned misbehaves with sane_cancel?"</a>
|
|
<!-- nextthread="start" -->
|
|
<!-- reply="end" -->
|
|
</ul>
|