On Mon, 25 Dec 2000, Brandon wrote:
> No, this is different. Your proposal messes with KSKs. My proposal is to
> create a new psuedo-keytype such as MMK, so:
> freenet:MMK@mapfile/filename
>
> The distinction may seem subtle but it doesn't mess up KSK or SSK
> parsing. You could even have a mapfile indexed by CHK:
> freenet:MMK@CHK@asdf/filename
>
> Another example:
> freenet:MMK@SSK@asdf/blah/filename
>
> The last one is iffy, but you have to have some way to use SSKs for map
> files, which is confusing unless you say that mapfile names can't have
> "/" in them, which I am comfortable doing.
>
> So what do you think of this way versus putting the mapfile name in all of
> the different keytypes?
I thought colons were forbidden in KSKs and SSKs, because the client
rejected my colon when I tried to insert it. I omitted the "freenet:KSK@"
and that confused it. With the freenet:KSK@, it worked. Bleah.
The thing is, who's really going to use the string ":/"? You aren't naming
your inserted keys "freenet:KSK@blah:/blah:/blah:/blah", are you?
Are you comfortable forbidding KSKs with two slashes in a row? It's
actually much prettier than ":/". And no sane person names their files
with two slashes in a row. It looks quite good:
freenet:CHK@rE9zY9IVJAqGZInGOF0d03L6ZeoOAwE,nmrAmhCGI3EBnKMALocq7A//index.html
freenet:pigdogjournal//index.html
etc. Mozilla, Netscape 4, IE, and Lynx all send the // unmunged. Hrmmm, do
any of them strip the second slash when changing directories... Netscape 4
doesn't, IE doesn't, Mozilla doesn't, Lynx doesn't. Yay!
If you saw how fast I just loaded thirty images across my network, and how
damn sexy that // looked (I typed "freenet:mork//index.html" and WHAM!),
you would agree with me. That's my opinion, and I'm sticking to it!
--
Mark Roberts
[EMAIL PROTECTED]
_______________________________________________
Freenet-dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/freenet-dev
