screwed. It is possible the remote saned will still send the bytes, even if
you call SANE_NET_CANCEL. There is no way (that I can tell) that the
communication link can recover.
Even the sends could incorrectly fail under heavy system loads, in fact I
believe the watch could cause a process deadlock. If the alarm triggers
before the actual read/write will the read timeout?
Has anyone thought about a simple frame around these things?
Brian Macy
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com