The wapi ought to cope with slashes

[kpreid]

From NEWS: "Slashes are discouraged in Tahoe file/directory names, since they cause problems when accessing the filesystem through the wapi"

I haven't looked in the implementation, but this shouldn't be a problem. In URLs, a path component can contain a slash; it just needs to be encoded: ​http://example.org/conjunctions/either%2for

If this doesn't automatically work already, I suspect that the wapi may have %-encoding issues (not encoding/decoding at the right times, or at all).

(I do not argue against (or for) discouraging slashes; merely that a URL-based system should be able to deal with them IF they occur.)

[davidsarah]

This bug seems inconsistent with the design decision made in #75.

I would argue against allowing slashes in Tahoe filenames, even at a low level. Almost all filesystems disallow slashes (and NULs), so we don't need them to interoperate with other filesystems. Having different rules about which filenames are allowed at different levels can only cause problems.

Note that the POSIX definition of a filename, at ​http://www.opengroup.org/onlinepubs/000095399/basedefs/xbd_chap03.html#tag_03_169 , is:

A name consisting of 1 to {NAME_MAX} bytes used to name a file. The characters composing the name may be selected from the set of all character values excluding the slash character and the null byte. The filenames dot and dot-dot have special meaning. A filename is sometimes referred to as a "pathname component".

I suggest resolving this as invalid. (We do need to think more carefully about what filenames are allowed, but that is covered by other bugs, such as #731.)

[zooko]

I agree with davidsarah, and note that #731 is about actually disallowing slashes (as well as other things).