Another SAR/DVS feature request
Brian Keefer
mgomes21 at cox.net
Fri Dec 6 04:29:45 UTC 2002
My small WIBNI solution is to make a URI that's pipable. One format that I
fantasized about is to declare multiple protocols in the start of the URI,
and mark the plumbing boundries with a "//".
> but it's hard to tell what the file name is, if you can't actually go
> through directories and members. For instance, how would you ask a
> user to insert a floppy containing:
>
> zip:///some/path/to/some.zip/another.zip/name2/name3
>
> Now is this:
> zip name: /some/path/to/some.zip/another.zip member name: name2/name3
file:zip:/some/path/to/some.zip/another.zip//name2/name3
> zip name: /some/path/to/some.zip member name: another.zip/name2/name3
file:zip:/some/path/to/some.zip//another.zip/name2.name3
> zip name: /some/path/to/some.zip/another.zip/name2 member name: name3
file:zip:/some/path/to/some.zip/another.zip/name2//name3
or even file:zip:zip:/some/path/to/some.zip//another.zip//name2/name3,
where name2/name3 is inside 2 layers of .zip files.
CONS: breaks bad pathname concatenation that hopes // is meaningless.
Looks too much like a selector gone bad. What does absolute|relative path
mean to the ///?
PROS:
"ssh:smb:gzip:tar:/myworkplace.com//bobsComputer/foo/bar.tar.gz//.//baz/thefile.doc".
Am I sick, or does that not look cool?
More information about the Squeak-dev
mailing list
|