https://issues.apache.org/bugzilla/show_bug.cgi?id=47693
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |[email protected] Resolution|WONTFIX | --- Comment #2 from [email protected] 2009-09-29 01:38:29 PDT --- Perhaps it won't be feasible in terms of internal state management inside the server, but the solution would be to use the following sequence: open the file, get it's length, read the file, close the file instead of: open the file, get it's length, close the file, open the file, read the file, close the file. Note that the interference with file that I'm talking about is not an arbitrary modification to the file, but only the case where the file is replaced by another file. This is a typical filesystem operation for doing a "clean" / "atomic" modification to a file: write a new copy of the file content to a temporary file, then replace the target file by the temporary file. Reopening to get feedback on the feasibility of the proposed solution... -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
