Re: Eeck.. network protocol

Brian Macy (bmacy@sunshinecomputing.com)
Tue, 9 Jun 1998 21:44:32 -0700

>Can you be more specific? If you could give the (or one) exact
>sequence of events that would cause trouble, it'll be much easier to
>make this discussion useful.

I may be missing something but either of the two might be a problem...

1)
Client: Sends a command
Server: heavy load
Client: timeout on response
Server: receives command and responds
Client: Sends a command
Client: Gets response for previous command

2)
Client: sets alarm
Client: heavy load
Client: alarm timeouts
Client: quit called
Client: exits // just because he was too busy and never sent the packet out
the port

Actually the alarms are 300 seconds so load will not likely be a problem. It
looks like SANE handles the race conditions by simply shutting down if
anything goes wrong. I guess I was looking for something a little more
robust.

Brian Macy

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