Ben Stanley wrote:
> I agree with this. If the connection is dropped, then xsane should start a
> new connection. I consider the current behaviour of xsane in this respect to
> be a bug, although I realise that it comes about because the saned protocol
> is incomplete, and is recognised to be incomplete in the README (now that I
> remember reading it there...).
Hi Ben, hi Nick.
SANE defines an API between a frontend and a backend.
The SANE network part shall be invisible for the frontends and the
backends. This means that sane-net has to behave like a normal backend
and saned as a normal frontend. Everything that is related to the
network communication has to be done in sane-net and saned and has
to be invisible for the frontend and the scanner-driver-backend.
It is not possible to start a new network connection because
you start a new backend that does not now about the option settings
What must be implemented is a communication between saned and sane-net
that makes sure that saned does not die as long as sane-net (and the
frontend) is still running.
-- Homepage: http://www.rauch-domain.de sane-umax: http://www.rauch-domain.de/sane-umax xsane: http://www.xsane.org E-Mail: mailto:Oliver.Rauch@rauch-domain.de
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail email@example.com
This archive was generated by hypermail 2b29 : Sun Jun 03 2001 - 23:44:42 PDT