Re: Starting a discussion about SANE and TWAIN...

Andreas Beck (becka@rz.uni-duesseldorf.de)
Sat, 14 Aug 1999 20:06:57 +0200

> > > -> TWAIN to SANE-FRONTEND-wrapper
> > That is the hard part, especially, if we try to:
> > > The wrapper and the standard has to be compatible to
> > > all operating systems.
> > On Unix I would use some form of IPC. Probably pipes. How is it handled on
> > Win and MacOS now ?
> > I think pipes are probably best for starters, as they enforce a streamed
> > protocol, that can definitely be used on any platform of interest, at worst
> > using a TCP/IP connection to localhost, which every platform that is in use
> > nowadays should support.

> I think we should have a look how TWAIN does this on windows/mac.

from DLLs using a tokenized, single-entry-point system.

This is conceptually similar to using a streamed interface and could
probably be easily transformed into that.

> Of course using pipes is the simplest way to do it, but as far as I know there
> are no pipes on Windows and Mac.

We are talking about interfacing SANE frontends from a TWAIN layer. That is,
we are talking about an environment, where SANE frontends can run. That
assumes we have something like Cygwin or similar, which gives us Posixish
features. For a fully native solution, other communication paths are
possible, as streamed transfers can take place on about any medium.

> The wrapper should not do a lot. May be we can include it into the frontends
> like a sanei_* routine, so the frontend itself gets a TWAIN interface.

Yes.

CU, Andy

-- 
= Andreas Beck                    |  Email :  <andreas.beck@ggi-project.org> =

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