[Webfunds-commits] html/guide/faq Makefile index.html
Ian Grigg
iang@cypherpunks.ai
Mon, 19 Mar 2001 11:50:45 -0400 (AST)
iang 01/03/19 11:50:45
Modified: guide index.html ricardian.html
Added: guide/faq Makefile index.html
Log:
new FAQ on proxies, more notes in ricardian
Revision Changes Path
1.17 +2 -0 html/guide/index.html
Index: index.html
===================================================================
RCS file: /home/webfunds/cvsroot/html/guide/index.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- index.html 2001/02/16 14:51:34 1.16
+++ index.html 2001/03/19 15:50:44 1.17
@@ -10,6 +10,8 @@
<h1>Doco</h1>
<ul><li>
+ A start at a <a href="faq/index.html">FAQ</a>.
+ </li><p><li>
Our one-size-fits-all
<a href="show_time/index.html">Slide Show</a>
presented at
1.6 +46 -10 html/guide/ricardian.html
Index: ricardian.html
===================================================================
RCS file: /home/webfunds/cvsroot/html/guide/ricardian.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- ricardian.html 2001/03/04 12:17:47 1.5
+++ ricardian.html 2001/03/19 15:50:44 1.6
@@ -127,19 +127,22 @@
<ol><li>
Human parsable
</li><li>
+ Document is printable
+ </li><li>
Program parsable
</li><li>
- Represents a contract
+ All forms (displayed, printed, parsed) are manifestly equivalent
</li><li>
- Can be identified uniquely
+ Represents a legal contract
</li><li>
- Signed by Issuer
+ Can be identified securely, where security means any
+ attempt to pervert the linkage between a reference and
+ the contract is impractical.
</li><li>
- All pertinant information in one single document
- </li><li>
- Document is printable
+ Signed by Issuer
</li><li>
- All forms (displayed, printed) are manifestly equivalent
+ All pertinant information in one single document,
+ including signature and parties.
</li><li>
Supported by financially capable PKI (such as OpenPGP)
</li><li>
@@ -316,6 +319,9 @@
<h4><a name="vouchers_comparison">Comparison</a></h4>
<p>
+Does the Voucher meet the
+<a href="#requirements">requirements</a>
+if the Ricardian Contract?
In terms of the contrast between Ricardian Contracts
and Fujimura/Terada Vouchers
(what this page is more properly about),
@@ -400,7 +406,7 @@
<td bgcolor="#FFFFF0">Contractual
</td><td> yes
</td><td bgcolor="#FF8800"> no
- </td><td> lacks defined signature, PKI, human parsability, unique id
+ </td><td> lacks defined signature & PKI, human parsability, unique id
</td>
</tr><tr>
@@ -415,9 +421,39 @@
<p> </p>
<p>
As a contract in the terms that the Ricardian Contract
-attempts to meet, the Voucher does not succeed. However,
-it may be that we can use the Voucher ID as the starting
+attempts to meet, the Voucher might not succeed. That
+is somewhat unjust as there is no indication that the
+requirements of the Voucher are intended to be of a
+contractual form, merely that they are suitable for
+describing loyalty systems and ticketing and the like.
+</p>
+
+<p>
+However, it may be that we can use the Voucher ID as the starting
point for the future XML format for the Ricardian Contract.
+</p>
+
+<h3><a name="fsml">FSML</a></h3>
+
+<p>
+A consortium has defined an
+<a href="http://www.echeck.org/"> eCheck </a>
+format written in
+SGML (not quite XML) for the purposes of transmitting
+cheques between parties. These are definately banking
+cheques, not SOX cheques.
+</p>
+
+<p>
+The Document Formatting Rules in the standard may be of interest.
+It describes characters, tags, lines,
+and whitespace, all pretty much as we do things.
+</p>
+
+<p>
+The rest of the document is not so useful, it includes
+too many assumptions about cheques and protocols. It's
+also locked up in PDF and can't easily be worked with.
</p>
</body></html>
1.1 html/guide/faq/Makefile
Index: Makefile
===================================================================
TARGET_DIR=guide/faq
include ../../Make_common
export: \
index.a \
1.1 html/guide/faq/index.html
Index: index.html
===================================================================
<html><head>
<title>FAQ</title>
</head><body>
<P>
<a href="../index.html">Up!</a>
</P>
<h1>FAQ</h1>
<h2>Proxies</h2>
<pre><i>
<someone> wrote:
>
> WebFunds won't work on our development machines.
>
> Because we're on a 10.0.0.0 network hidden from the world.
>
> ah. how tough is it going to be to stick a proxy support in there?
</i></pre>
<p>
There are several answers to this, none are necessarily comprehensive...
</p>
<h3>Transparent Proxies</h3>
<p>
Ask your sysadm to install a transparent proxy...
</p>
<h3>JVM proxy</h3>
<p>
This
<a href="http://www.ibiblio.org/javafaq/">
FAQ</a>
explains how to set up the proxy within the JVM:
</p>
<blockquote>
<a href="http://www.ibiblio.org/javafaq/javafaq.html#proxy">
http://www.ibiblio.org/javafaq/javafaq.html#proxy</a>
</blockquote>
<p>
Let us know if it works. <i>SOX over socks</i> is definately a cool
feature to have.
</p>
<h3>WebFunds proxy</h3>
<p>
The code is in there to set up the properties,
so in the startup run file or doze equivalent
add the flags:
</p>
<pre>
-pb true -ph hostname -pp portnum
</pre>
<p>
(once only, it should store the flags in the properties file, which
is located at user/props.dat )
</p>
<p>
However the properties are currently ignored by the socket
code.
</p>