kopia lustrzana https://gitlab.com/sane-project/website
69 wiersze
2.7 KiB
HTML
69 wiersze
2.7 KiB
HTML
<!-- received="Tue Jun 9 21:45:33 1998 PDT" -->
|
||
<!-- sent="Tue, 9 Jun 1998 21:44:32 -0700" -->
|
||
<!-- name="Brian Macy" -->
|
||
<!-- email="bmacy@sunshinecomputing.com" -->
|
||
<!-- subject="Re: Eeck.. network protocol" -->
|
||
<!-- id="" -->
|
||
<!-- inreplyto="Eeck.. network protocol" -->
|
||
<title>sane-devel: Re: Eeck.. network protocol</title>
|
||
<h1>Re: Eeck.. network protocol</h1>
|
||
<b>Brian Macy</b> (<a href="mailto:bmacy@sunshinecomputing.com"><i>bmacy@sunshinecomputing.com</i></a>)<br>
|
||
<i>Tue, 9 Jun 1998 21:44:32 -0700</i>
|
||
<p>
|
||
<ul>
|
||
<li> <b>Messages sorted by:</b> <a href="date.html#84">[ date ]</a><a href="index.html#84">[ thread ]</a><a href="subject.html#84">[ subject ]</a><a href="author.html#84">[ author ]</a>
|
||
<!-- next="start" -->
|
||
<li> <b>Next message:</b> <a href="0085.html">jnealy@icubed.net: "os/2 and Parallel scanners"</a>
|
||
<li> <b>Previous message:</b> <a href="0083.html">David Mosberger-Tang: "Re: Eeck.. network protocol"</a>
|
||
<li> <b>Maybe in reply to:</b> <a href="0037.html">Brian Macy: "Eeck.. network protocol"</a>
|
||
<!-- nextthread="start" -->
|
||
<!-- reply="end" -->
|
||
</ul>
|
||
<!-- body="start" -->
|
||
<i>>Can you be more specific? If you could give the (or one) exact</i><br>
|
||
<i>>sequence of events that would cause trouble, it'll be much easier to</i><br>
|
||
<i>>make this discussion useful.</i><br>
|
||
<p>
|
||
<p>
|
||
I may be missing something but either of the two might be a problem...<br>
|
||
<p>
|
||
1)<br>
|
||
Client: Sends a command<br>
|
||
Server: heavy load<br>
|
||
Client: timeout on response<br>
|
||
Server: receives command and responds<br>
|
||
Client: Sends a command<br>
|
||
Client: Gets response for previous command<br>
|
||
<p>
|
||
2)<br>
|
||
Client: sets alarm<br>
|
||
Client: heavy load<br>
|
||
Client: alarm timeouts<br>
|
||
Client: quit called<br>
|
||
Client: exits // just because he was too busy and never sent the packet out<br>
|
||
the port<br>
|
||
<p>
|
||
Actually the alarms are 300 seconds so load will not likely be a problem. It<br>
|
||
looks like SANE handles the race conditions by simply shutting down if<br>
|
||
anything goes wrong. I guess I was looking for something a little more<br>
|
||
robust.<br>
|
||
<p>
|
||
Brian Macy<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="0085.html">jnealy@icubed.net: "os/2 and Parallel scanners"</a>
|
||
<li> <b>Previous message:</b> <a href="0083.html">David Mosberger-Tang: "Re: Eeck.. network protocol"</a>
|
||
<li> <b>Maybe in reply to:</b> <a href="0037.html">Brian Macy: "Eeck.. network protocol"</a>
|
||
<!-- nextthread="start" -->
|
||
<!-- reply="end" -->
|
||
</ul>
|