kopia lustrzana https://gitlab.com/sane-project/website
62 wiersze
3.0 KiB
HTML
62 wiersze
3.0 KiB
HTML
<!-- received="Sun Feb 28 10:31:27 1999 PST" -->
|
|
<!-- sent="Sun, 28 Feb 1999 10:31:14 -0800" -->
|
|
<!-- name="David Mosberger-Tang" -->
|
|
<!-- email="David.Mosberger@acm.org" -->
|
|
<!-- subject="Re: Porting SANE backends" -->
|
|
<!-- id="199902281831.KAA01895@panda.mostang.com" -->
|
|
<!-- inreplyto="36D5D35E.990ADB1B@wolfsburg.de" -->
|
|
<title>sane-devel: Re: Porting SANE backends</title>
|
|
<h1>Re: Porting SANE backends</h1>
|
|
<b>David Mosberger-Tang</b> (<a href="mailto:David.Mosberger@acm.org"><i>David.Mosberger@acm.org</i></a>)<br>
|
|
<i>Sun, 28 Feb 1999 10:31:14 -0800</i>
|
|
<p>
|
|
<ul>
|
|
<li> <b>Messages sorted by:</b> <a href="date.html#224">[ date ]</a><a href="index.html#224">[ thread ]</a><a href="subject.html#224">[ subject ]</a><a href="author.html#224">[ author ]</a>
|
|
<!-- next="start" -->
|
|
<li> <b>Next message:</b> <a href="0225.html">David Mosberger-Tang: "Re: 16-bit frames and interleaving"</a>
|
|
<li> <b>Previous message:</b> <a href="0223.html">becka@rz.uni-duesseldorf.de: "Re: Info Peripherals' ImageReaderISA"</a>
|
|
<!-- nextthread="start" -->
|
|
<!-- reply="end" -->
|
|
</ul>
|
|
<!-- body="start" -->
|
|
<i>>>>>> On Sun, 28 Feb 1999 18:21:32 +0200, Milon Firikis <<a href="mailto:milonf@ariadne-t.gr">milonf@ariadne-t.gr</a>> said:</i><br>
|
|
<p>
|
|
Milon> Note that the objective is to hide all Unix specific<br>
|
|
Milon> functions from the backend much like the sanei_scsi_ routines<br>
|
|
Milon> do for scsi operations.<br>
|
|
<p>
|
|
You're wrong. Yes, the _API_ must be OS independent but the sample<br>
|
|
implementation that we distribute is developed and intended for<br>
|
|
POSIX-compatible systems. If we can port that source to other<br>
|
|
platforms easily and cleanly, great, but to say that we want to hide<br>
|
|
all UNIX/POSIX specific functions is silly.<br>
|
|
<p>
|
|
The issue with fork() is that it's hard (inefficient) to implement on<br>
|
|
any system that doesn't have virtual memory. However, threads do not<br>
|
|
necessarily solve the problem either. E.g., on systems supporting<br>
|
|
user-level threads only (e.g., SunOS, HP-UX up to 10.20, etc.), a<br>
|
|
thread may not even help for SANE backends.<br>
|
|
<p>
|
|
Anyhow, if someone modifies the backends to abstract fork() in an<br>
|
|
elegant way, I'd be happy to merge in such patches. But if it can't<br>
|
|
be done cleanly, you'd be better of creating and maintaining your own<br>
|
|
SANE implementation. It's perfectly OK to have multiple SANE<br>
|
|
implementations as long as they can interoperate.<br>
|
|
<p>
|
|
--david<br>
|
|
<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="0225.html">David Mosberger-Tang: "Re: 16-bit frames and interleaving"</a>
|
|
<li> <b>Previous message:</b> <a href="0223.html">becka@rz.uni-duesseldorf.de: "Re: Info Peripherals' ImageReaderISA"</a>
|
|
<!-- nextthread="start" -->
|
|
<!-- reply="end" -->
|
|
</ul>
|