Fwd: [jbosscache-dev] RE: http://jira.jboss.com/jira/browse/JBCACHE-644

[Manik Surtani]

I suppose given that we're not even recommending the FCL for most  
production use cases, perhaps just log a warning in the FCL when such  
characters are encountered, warning of the lack of portability and  
the potential for an IOException?


>
>
>
> On 23 Oct 2006, at 17:13, Galder Zamarreno wrote:
>
>> Looking at this further, what do we wanna do if we encounter one  
>> of this characters when creating the file/directory?
>>
>> We could substitute them for other allowed characters, but it  
>> would also mean that a get operation would have to translate the  
>> fqn to the allowed fqn with the substituted characters. We would  
>> need some kind of mapping between the original fqn and the  
>> translated one.
>>
>> Is it really worth doing this? The more I think about it, the more  
>> I feel that it seems like adding an unnecessary layer of  
>> complexity to the FCL, especially when there's a very easy  
>> alternative to it, which is not using those characters.
>>
>> I found this article talking about differences between Linux, Mac  
>> and Windows: http://linux.wordpress.com/2006/07/23/linux-mac- 
>> windows-file-name-friction/
>>
>> Windows is definitely the most restrictive, but Linux and Mac  
>> might sound more restrictive in this sense, but might have to get  
>> around it to create files with these characters (use ' '  
>> characters, or '\').
>>
>> It ends up saying:
>>
>> Avoid using these characaters
>> for maximum portability
>>
>> Asterisk 	*
>> Colon 	:
>> Back slash 	\
>> Forward slash 	/
>> Less Than 	<
>> Greater Than 	>
>> Pipe 	|
>> Quote 	"
>> Question mark 	?
>>
>> What do you think? Is it really worth it?
>>
>> Galder Zamarreño
>> Sr. Software Maintenance Engineer
>> JBoss, a division of Red Hat
>>
>>
>> -----Original Message-----
>> From: jbosscache-dev-bounces at lists.jboss.org [mailto:jbosscache- 
>> dev-bounces at lists.jboss.org] On Behalf Of Galder Zamarreno
>> Sent: 20 October 2006 12:00
>> To: Manik Surtani
>> Cc: jbosscache-dev at lists.jboss.org
>> Subject: [jbosscache-dev] RE: http://jira.jboss.com/jira/browse/ 
>> JBCACHE-644
>>
>> 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 at jboss.org]
>> Sent: 20 October 2006 11:57
>> To: Galder Zamarreno
>> Cc: jbosscache-dev at 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 at jboss.org
>> Telephone: +44 7786 702 706
>> MSN: manik at 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
>>>
>>>
>>
>>
>> _______________________________________________
>> jbosscache-dev mailing list
>> jbosscache-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosscache-dev
>