On Mon, 2008-08-18 at 16:20 -0700, John Caruso wrote: > It's not difficult to come up with examples where it might happen, > BTW...say, a web service that returns the result of an operating system > command to a user.
The command is named ns_returnfile. The expectation is that you are returning a "file", not a web service resource. The expectation is that the file will be around for longer than one second before being deleted and replaced. The fact that the documentation doesn't say this is unimportant. Inodes are reused, this is part of how the filesystem works. You could run into the same problem with an archive program. A file of the same inode, name, size and age is created replacing the old file. Most archive programs would not understand that the file contents had changed. Is it a bug? No. It is called a practical limitation. Anyway: no bug, just how it works. The only bug is how ns_returnfile is being used in the example. tom jackson -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
