On 5/22/06, David McNab <[EMAIL PROTECTED]> wrote:
/keys/[EMAIL PROTECTED]
- performs a GET of the given key from freenet, and allows it
to be read like a file. First line is <mimetype>\n
/privatekeys/[EMAIL PROTECTED]/name
- the filename '[EMAIL PROTECTED]' is the private key
corresponding to /keys/[EMAIL PROTECTED]/name
- reading from this file produces a single line, the equivalent
public key
- writing to this file performs a freenet PUT. First line written
should be <mimetype>\n, then the raw key data
I don't like the idea of the MIME type being the first line of the
file; it's something that will have to be stripped when the file is
moved to the rest of the system or worked on by standard programs.
I'd rather have a directory for each key. Assuming the freenet fs has
been mounted on /freenet, downloads would look like:
$ cd /freenet/downloads
$ mkdir [EMAIL PROTECTED]; cd [EMAIL PROTECTED]
$ tail status
<lots of messages>
done
$ cat mimetype
text/plain
$ cat name
dissident_report
$ cat data > ~/`cat name`
$ ls ~/dis*
/usr/glenda/dissident_report
$
And uploads would look like:
$ cd /freenet/uploads
$ cat new
42
$ cd 42
$ cat text/plain > mimetype
$ cat ~/manifesto > data
$ tail status
<various messages>
done
$ cat key
[EMAIL PROTECTED]
$
The influence of Plan 9 (the original source of user-space
filesystems) may be visible here.
--Joel
_______________________________________________
chat mailing list
chat@freenetproject.org
Archived: http://news.gmane.org/gmane.network.freenet.general
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/chat
Or mailto:[EMAIL PROTECTED]
