Allan Wilson wrote:is there some "optimization" going on? I notice that when I update certain channels (manually), the .rss file doesn't seem to get updated, but the channel shows a new Last Updated time.
If the web server returns an HTTP 304 Not Modified, the .RSS file is not re-written (since it hasn't changed) but the channel is flagged as having been updated.
Allan Wilson wrote:Maybe modification date/time changes dynamically throughout a file's "creating" lifetime, which would account for the initial zero length; however, I (perhaps naively) expect modification time not to be updated/apply until a file is closed...
You would have to write a little test app to confirm this but I would agree that this is naive
For example, what if a file was opened allowing multiple readers/writers. If somebody modified the file but still kept it open, I would want the other processes to see a new modification time.
I'll have a look at the double update of the .RSS file as well. Awasu opens the file and then gets the feed before writing it out i.e. there's a delay between opening the file and writing the feed out. So you may well be seeing two file modified notifications.