I'd stick to general rules.
Cheers,
Galder ZamarreƱo
Sr. Software Maintenance Engineer
JBoss, a division of Red Hat
-----Original Message-----
From: Manik Surtani [mailto:manik@jboss.org]
Sent: 20 October 2006 11:57
To: Galder Zamarreno
Cc: jbosscache-dev(a)lists.jboss.org
Subject: Re:
http://jira.jboss.com/jira/browse/JBCACHE-644
Yes, I think so ...
Just be generic. Perhaps the FileCacheLoader could take an optional
property containing a list of OS-specific illegal characters for the
deployed platform, but then again if someone can specify this, they'd
know not to use these characters in the cache anyway.
I'd just stick with the generic illegal chars.
--
Manik Surtani
Lead, JBoss Cache
JBoss, a division of Red Hat
Email: manik(a)jboss.org
Telephone: +44 7786 702 706
MSN: manik(a)surtani.org
Yahoo/AIM/Skype: maniksurtani
On 20 Oct 2006, at 10:48, Galder Zamarreno wrote:
There's a hard limit in Windows by which a file path cannot be
bigger than 255 characters, so that's an OS limit itself.
Illegal characters vary depending on the OS, but there's some that
apply to all OS.
How do you wanna approach this? Shall we focus on limitations
applying to all OS? I doubt we wanna be coding something that is
dependant on the OS.
Galder ZamarreƱo
Sr. Software Maintenance Engineer
JBoss, a division of Red Hat