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=23750>. 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=23750 [PATCH] "segments" timestamp patch ------- Additional Comments From [EMAIL PROTECTED] 2003-10-22 04:19 ------- Here's an improved patch for this problem. As discussed on the mailing list, it creates timestamp files of the format filename.<timestamp> where timestamp is System.currentTimeMillis(). it handles low resolution system timers by using the same trick RAMDirectory does, checks for an existing file with that timestamp, sleeps for one nanosecond, then tries again. touchFile deletes all existing timestamps files and creates a new one. One issue I am unclear on is how this would behave in a multithreaded call, and whether there are any issues with the deletes/ create being non-atomic. Anyway, all the testcases pass. I'd appreciate review of this patch, and if good enough, its inclusion in RC2! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
