Support of named attributes in jdk7
Alan.Bateman at Sun.COM
Tue Jan 27 06:46:01 PST 2009
Jean-Pierre André wrote:
> Yes, of course the names have to be translated when needed.
> We have a long tradition of converting UTF8 to and from UTF16,
> including in special situations as needed for Hangul. Translating
> attribute names will of course be done as file names are.
Is the charset a mount or FUSE option? Just wondering, as there be
issues when default encoding is not UTF-8 (this is determined at startup
based on the locale and operating system).
> On the contrary, we do not interpretation of the attribute value.
> We expect the application to deal with it in a consistent way, just
> like when putting data inside a file.
> In the Xdd.java example, the value was a string, and I had no
> problem, but there surely would have been if the Windows version
> had put UTF16 and the Linux one had interpreted it as UTF8.
> You must have defined a consistent representation of the value.
I agree that the value isn't a problem. In the Xdd sample it encodes the
String using the default encoding so there may be issues but this is
completely up to the application.
More information about the nio-dev