kopia lustrzana https://gitlab.com/sane-project/website
75 wiersze
3.4 KiB
HTML
75 wiersze
3.4 KiB
HTML
<!-- received="Mon Aug 16 01:40:54 1999 PDT" -->
|
||
<!-- sent="Mon, 16 Aug 1999 10:41:06 +0200" -->
|
||
<!-- name="Ewald R. de Wit" -->
|
||
<!-- email="ewald@pobox.com" -->
|
||
<!-- subject="Re: SANE V2" -->
|
||
<!-- id="" -->
|
||
<!-- inreplyto="19990816014243.A3689@rz.uni-duesseldorf.de" -->
|
||
<title>sane-devel: Re: SANE V2</title>
|
||
<h1>Re: SANE V2</h1>
|
||
<b>Ewald R. de Wit</b> (<a href="mailto:ewald@pobox.com"><i>ewald@pobox.com</i></a>)<br>
|
||
<i>Mon, 16 Aug 1999 10:41:06 +0200</i>
|
||
<p>
|
||
<ul>
|
||
<li> <b>Messages sorted by:</b> <a href="date.html#193">[ date ]</a><a href="index.html#193">[ thread ]</a><a href="subject.html#193">[ subject ]</a><a href="author.html#193">[ author ]</a>
|
||
<!-- next="start" -->
|
||
<li> <b>Next message:</b> <a href="0194.html">becka@rz.uni-duesseldorf.de: "Re: SANE V2"</a>
|
||
<li> <b>Previous message:</b> <a href="0192.html">becka@rz.uni-duesseldorf.de: "Re: 2 scanners under Linux"</a>
|
||
<!-- nextthread="start" -->
|
||
<!-- reply="end" -->
|
||
</ul>
|
||
<!-- body="start" -->
|
||
Andreas Beck (<a href="mailto:becka@rz.uni-duesseldorf.de">becka@rz.uni-duesseldorf.de</a>) wrote:<br>
|
||
<p>
|
||
<i>> Now we see demand for transferring data that is not accurately described by</i><br>
|
||
<i>> getparm. Thus I propose to do the simple thing and basically ignore getparm</i><br>
|
||
<i>> stuff and just transfer some streamed data.</i><br>
|
||
<i>> </i><br>
|
||
<i>> Now this alone would be not too good, as it leaves no idea what the data </i><br>
|
||
<i>> and its format actually is. </i><br>
|
||
<i>> Thus I propose to add a generic content description system for such data.</i><br>
|
||
<i>> Mime seems like a good choice, as said above. </i><br>
|
||
<p>
|
||
Mime would just tell you what sort of data stream it is but not<br>
|
||
anything about the data itself. You would still have to get<br>
|
||
the associated parameters in some other way. Not only the standard<br>
|
||
parameters, but possibly also others (like exposure time). To do this<br>
|
||
in a truly general way one could use XML.<br>
|
||
<p>
|
||
<i>> 2. Add a single bew frametype that announces the transmission of arbitrarily</i><br>
|
||
<i>> formatted data. Add two identification fields somewhere that give the</i><br>
|
||
<i>> mimetype and optionally a proposed filename for the data, so one can </i><br>
|
||
<i>> correctly detect and handle the type of data.</i><br>
|
||
<p>
|
||
Given the mimetype and filename you now know how to dump the data to a<br>
|
||
file in a format of your pleasing, but nothing more.<br>
|
||
<p>
|
||
What I'm saying is, the mimetype stuff is more general but not general<br>
|
||
enough. Perhaps in the future we can use XML for the communication<br>
|
||
between backend and frontend, and we can use Netscape 9.0 as a<br>
|
||
frontend to surf our scanner with. But for the more immediate future,<br>
|
||
what I would like to see is a more incremental upgrade to the current<br>
|
||
standard (perhaps better call it 1.1 instead of 2.0). That is, to just<br>
|
||
add some new frame formats and well known options.<br>
|
||
<p>
|
||
<pre>
|
||
--
|
||
-- Ewald
|
||
<p>
|
||
<p>
|
||
<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="0194.html">becka@rz.uni-duesseldorf.de: "Re: SANE V2"</a>
|
||
<li> <b>Previous message:</b> <a href="0192.html">becka@rz.uni-duesseldorf.de: "Re: 2 scanners under Linux"</a>
|
||
<!-- nextthread="start" -->
|
||
<!-- reply="end" -->
|
||
</ul>
|