The problem could be solved **SO** simply.
Let's assign two meanings to the single slash.
1) After 'SSK@blah', the '/' means 'a ssk subspace identifier follows,
terminated by another slash or by end of uri'
2) Anywhere else, the '/' means 'msk' - telling the requesting client to
look up the matching document in the map.
This is (i) Unambiguous, (ii) Deterministic, (iii) Easy to parse, (iv)
Consistent, (v) Compatible with much more software than '//'.
To call a piece of third-party 'broken' for not transparently dealing with
'//' is ludicrous - would anyone say that 'ht://dig', perhaps the most
popular search engine in Linux, is therefore 'broken'??
Example:
SSK@blahblah/name1/name2/name3.html - retrieves key 'SSK@blahblah/name1' and
looks up a document called 'name2/name3.html' in the map.
The only price to pay is very modest - that '/' be disallowed within
subspace identifiers. Not too tragic surely?
David
----- Original Message -----
From: "Stefan Reich" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, July 16, 2001 11:23
Subject: Re: [freenet-chat] MSKs "//" breaks wget et al.
> >> 3) 'SSK@blahblah/sitename/index.html' and ban slashes in subspace
> >> identifiers?
> >
> >I'd like to vote *against* number 3. We need to permit subdirectories,
> >or else large freesites would be a major pain.
>
> Subdirectories are still ok, only the freesite identifier ("snarfoo") is
not
> allowed to contain slashes. I haven't ever seen such an identifier contain
a
> slash anyway. Putting a slash there smells like trouble in the first
place -
> it's what computer people have gotten used to avoiding instinctively: no "
> in file names, no : in directories, no spaces in host names...
>
> -Stefan
>
>
> _______________________________________________
> Chat mailing list
> [EMAIL PROTECTED]
> http://lists.freenetproject.org/mailman/listinfo/chat
>
_______________________________________________
Chat mailing list
[EMAIL PROTECTED]
http://lists.freenetproject.org/mailman/listinfo/chat
