You are viewing a plain text version of this content. The canonical link for it is here.

Posted to slide-dev@jakarta.apache.org by bu...@apache.org on 2002/04/29 18:59:08 UTC

DO NOT REPLY [Bug 8250] - Failed to write tmp file if the file path is very long

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8250>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8250

Failed to write tmp file if the file path is very long

jericho@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |REMIND



------- Additional Comments From jericho@apache.org  2002-04-29 16:59 -------
Yes, we should do that using digest function that hasn't lengthened the file 
name.  
If we desn't use any cryptographical functions, simply we can use the hashCode 
from String class, I guess.  It is never over 32 digit,I believe.  ;-)
Since it's just temporary and deleted very right, I will stay it alone for 
now...   Instead of it, the report is set to REMIND.

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>