Yep, base64 is just an example. We need some kind of urlencode, but tailored for file names, so that names remain readable.
To avoid uppercase/lowercase collisions on Windows, we can restrict allowed characters to lowercase English letters and numbers, - and _, and escape everything else in some way. On Wed, Dec 27, 2017 at 5:36 PM, Dmitriy Setrakyan <dsetrak...@apache.org> wrote: > On Wed, Dec 27, 2017 at 6:25 AM, Vladimir Ozerov <voze...@gridgain.com> > wrote: > > > Having different policies for persistent and non-persistent caches sounds > > like a bad idea for me, because there could be troubles should user try > to > > switch to persistent mode. It would require code changes. > > > > Can we just escape all non-latin symbols (e.g. using base64), while > leaving > > the rest as is? With this approach in most cases cache name will remain > the > > same, and only multibyte characters would be affected. > > > > Agree, if we can keep cache names in human readable form. Would be nice to > see some examples. >
