File API: File's name property

As currently specified File's name property seems to be a code unit
sequence. In zip archives the resource's path is a byte sequence. I
don't really know what popular file systems do. Given that a File has
to be transmitted over the wire now and then, including it's name
property value, a code unit sequence seems like the wrong type. It
would at least lead to information loss which I'm not sure is
acceptable if we can prevent it (or at least make it more obvious that
it is going on, by doing a transformation early on).

We may also want to restrict "\" and "/" to leave room for using these
objects in path-based contexts later.


-- 
http://annevankesteren.nl/

Received on Thursday, 29 August 2013 14:49:11 UTC