DO NOT REPLY [Bug 22775] - Xindice hangs forever on blocking I/O call
| Newsgroups | gmane.text.xml.xindice.devel |
|---|---|
| Message-ID | <[email protected]> |
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=22775>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=22775 ------- Additional Comments From [email protected] 2007-04-20 06:04 ------- > Hm, why would you do this check every time? Wouldn't one time check at the > moment file is opened be enough? Not necessarily, if 1) File got corrupted after it has been opened (I'd rather believe that Xindice messed up its own file than it was some evil Xindice-truncating application) 2) File length and amount of pages are correct, but some pointer to the page got garbage in it and points to non-existing page. But I agree, it does sound a little paranoid. I'm not sure if it makes sense to check it at runtime, introduce a tool to check file integrity, or just fix a bug that caused corruption in the first place :) -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.