Given the widespread use of Base64Encoder and UUEncode/UUDecode,
it makes sense to have
this available for folks to use, rather than writing their own or
using sun.misc.*, which isn't available when a security manager is in place.
Given the lateness, it should be considered again during mustang.
I agree. I started talking to Ian about putting in a BASE64 en/decoder as a NIO charset maybe a year ago (We both got sidetracked and nothing came of it).
Although BASE64 is conceptually quite a different encoding to what NIO was designed for, it would nicely fit into the existing APIs. If it feels too strange we can define new APIs instead, but I believe we have to do something about BASE64 given its widespread use.