In hindsight, I realize I'm guilty again of ripping off a familiar paradigm - in this case, the unix filesystem.
Perhaps an extension on this syntax could be that when a 'path' is 'known' to relate to freenet, the '/freenet' could be dropped from the front of it. eg http://127.0.0.1:8081/chk/alphabetsoup or, in a CLI command, freenet_request /chk/alphabetsoup Also, my decision to place the '/msk' at the *end* of the path body is deliberate - imho 'msk' is more intuitively regarded as a postfix, not prefix, specifier. ----- Original Message ----- From: "David McNab" <[email protected]> To: <devl at freenetproject.org> Sent: Monday, June 04, 2001 03:15 Subject: [freenet-devl] URI Syntax - Next Generation > I reported earlier that certain Windows appz are censoring the '//' in MSK > URIs into '/' > A visit to www.tucows.com and other win s/w sites will quell any scepticism > here. > > But just tonight in my insomnia I read on Content of Evil that Windows XP > appz will be doing the same thing - changing '//' to '/', which effectively > bans freesites in their present syntax. > > (No, I won't gloat, and say that FreeWeb's proxy, which compiles and runs on > Linux, overcomes this). > > What I *am* saying is that it could be crucial to Freenet's long term > welfare to phase in another URI syntax, especially for MSKs. Despite the > apparent flippancy of my previous post on the subject, I'm quite serious on > this one. > > Here's a proposal for new URI syntaxes, which tunnel completely within http > URL syntax, and won't strike any problems. No more URI encoding/decoding > blues. No more '@' => %40 etc. > > These examples use FProxy URLs at port 8081, but the path schema is > applicable anywhere. > > CHKs > Old: http://127.0.0.1:8081/freenet:CHK at alphabetsoup > New: http://127.0.0.1:8081/freenet/chk/alphabetsoup > > SSKs > Old: http://127.0.0.1:8081/freenet:SSK at alphabet,soup/somepath > New: http://127.0.0.1:8081/freenet/ssk/alphabet,soup/somepath > > MSKs over SSKs > Old: > http://127.0.0.1:8081/freenet:MSK at SSK@alphabetsoup/sitename//dir1/dir2/file. > ext > New: > http://127.0.0.1:8081/freenet/ssk/alphabetsoup/sitename/msk/dir1/dir2/file.e > xt > > KSKs - Explicit > Old: http://127.0.0.1:8081/freenet:KSK at human-readable-name > New: http://127.0.0.1:8081/freenet/ksk/human-readable-name > > KSKs - Implicit > Old: http://127.0.0.1:8081/freenet:human-readable-name > New: http://127.0.0.1:8081/freenet/human-readable-name > > MSKs over Implicit KSKs > Old: http://127.0.0.1:8081/freenet:human-readable-name//dir1/dir2/file.ext > New: > http://127.0.0.1:8081/freenet/human-readable-name/msk/dir1/dir2/file.ext > > and so on. > > The tiny price to pay for this is that the strings 'freenet', 'chk', 'ssk', > 'svk' and 'msk' will be forever off-limits from KSK namespace. > > Imagine issuing the command: > freenet_request > /ssk/p0EFqjmDioSqKmYYORPrClUepi4QAgE/snarfoo/msk/index.html > > Thoughts anyone? > > Cheers > David > > -- > In the beginning was the WORD, and the WORD was unsigned, and the main(){} > was without form and void... > > > > _______________________________________________ > Devl mailing list > Devl at freenetproject.org > http://lists.freenetproject.org/mailman/listinfo/devl > _______________________________________________ Devl mailing list Devl at freenetproject.org http://lists.freenetproject.org/mailman/listinfo/devl
