----- Original Message -----
From: "David McNab" <[EMAIL PROTECTED]>
> > "//" is the prettiest, cleanest identifier for
> > denoting cdoc msk handling that I have seen.
>
> Again, '//' breaks a lot of third-party http software.
> Some software chokes when it sees '//'.
> Other software edits it to '/' which results in automatic 404s from
fproxy.
>
> The most acceptable solution I've seen is to use '/MSK/', and to deem the
> string 'MSK' to be a reserved word within SSK subspaces. The strongest
> objection I've heard against it is that it's 'ugly'. Surely less ugly than
> breaking software though.
The most acceptable solution I've seen so far is to use '//' and when fproxy
gets to it, it translates all '//'s in a href to '/msk/'. there is already
reading of the stream before it passes through. the overhead of changing a
small portion of it would be minimal at best.
> So, what's the totally unbearable thing about
> 'SSK@blahblah/sitename/MSK/index.html' then?
The cdoc parsing (the document which comes before the '//') works as
follows:
if a document is entirely metadata and no data, treat it as a msk access
with a name="".
if a document has both metadata and data /AND/ the key has a '//' in it,
treat the portion after the name up to the next '//' as the msk name. if
there is no text after the first '//', treat it as if the name=""
All redirects and such are msks, and not all of them are going to be
blatantly shown as such. Many but not all KSKs are going to be cdocs. what
sense does it make to force users to use 'KSK@blah/MSK/' ?
EVERY control document is potentially a MSK.
> Yet another solution is to declare '/' to be illegal within subspace
> identifiers.
> There is no compelling argument why it should be supported within 0.4
> Surely the pain of losing software choices is far greater than the pain of
> having to use another delimiter like '_' within subspace identifiers.
> With this solution, 'SSK@blahblah/sitename/index.html' is a legal freesite
> URI.
I'm so wholly against this I'm not even going to go into it.
> OK then folks - what's it gonna be?
> 1) 'SSK@blahblah/sitename//index.html' and be a pain?
> 2) 'SSK@blahblah/sitename/MSK/index.html' and ban 'MSK' within SSK
subspace
> identifiers? or
> 3) 'SSK@blahblah/sitename/index.html' and ban slashes in subspace
> identifiers?
>
> FProxy for 0.4 isn't written yet, FwProxy is being adapted to 0.4 now, and
> 0.4 has almost no freesites at present.
> Therefore, this is the perfect window of opportunity to agree on a
solution
> the whole freenet community can be proud of.
I cannot be proud of adding in a system for the entire freenet community and
watch hacks being added for a SINGLE type of content. You have found a
problem with existing web software, fix either the software or the http
interface to freenet. Do not make your changes global everywhere.
Furthermore, there /is/ other data entering the 0.4 system which relies on
'//'. The use of '/MSK/' is not only ugly, as probably I put it, but so
purely and simply a hack for one type of content against ALL other types of
content which may be added to freenet. As you yourself tried to explain,
people dislike it when there are reserved symbols in a system. The current
reserved symbols in SSKs are ' ' and '//'. The first is a convenience to
keep file sane and is automatically converted to '+' by the system. The
second is unclean, but not only is attractive in it's ability to show the
user the logical breaks in the system, but very rare to occur accidentally.
Much more rare than '/MSK/' to occur accidentally.
> Votes please?
As my vote has always been, #1.
> David
-Mathew
_______________________________________________
Chat mailing list
[EMAIL PROTECTED]
http://lists.freenetproject.org/mailman/listinfo/chat
