Re: Message buffers associated with files?

[Scott Blachowicz <scott@statsci.com>]

> The issues with nngnats are even more difficult--files change, and you
> want to notice when they do.  Not only can the content change, but the
> status can change as well--essentially, the back end wants to keep
> track of some of the flags.  And some files you want to see again
> whenever they change, while others you don't want to see again.  This
> could be done through scoring, but the ideal thing would be to
> redefine dormancy as articles which magically become either unread or
> ticked when they change.  (This works well with gnats, since you
> should never have followups; you just keep adding to the same
> document.)

Another [probably full of holes] approach could be to have things like
file update time used to synthesize a "message-id" for the files. That
way, if the file changes, its message-id changes and it becomes a "new
message" as far as a news reader is concerned. Maybe there could be some
smarts in there to consider all revisions of the same file as part of the
same thread? Hmmm...I suppose that also means an automatic "cancel" on the
previous "message-id" too.

Just some thought/brick-bat fodder...

Scott Blachowicz  Ph: 206/283-8802x240   Mathsoft (Data Analysis Products Div)
                                         1700 Westlake Ave N #500
scott@statsci.com                        Seattle, WA USA   98109
Scott.Blachowicz@seaslug.org