Monday, 7 October 2002

Action plan Hey, that doesn't sound necessary.  Why don't I: only operate on the cache, and just treat it like a FIFO buffer. Keep the last n comments (where n = 10, 15, or whatever the server operator wants). When a new comment gets posted, drop it on the end of the table, and erase the first post if the new one pushes the number of posts over the limit. After saving a new comment, rebuild the RSS feed.  Save it somewhere near the cached comment counts. 11:01:06 PM    comment [][Macro error: Can't call the script because the name "liveTopicsSuite" hasn't been defined.]

Hacking comment RSS feeds into Frontier Time for a proof of concept.  I'm working with the part of Radio Community Server that lives inside Manila. Aha!  Finally found it: the comments are in manilaWebsites.root, in rcsCommentsManilaWebsite.#newsSite.radioHosting.comments. The comments themselves are stored in a Manila discussion. Metadata about comments are in comments.users.[usernum].[postid].  This is a table with two items: link, the URL of the post the comments are about. msgnum, the thread ID from the discussion system that holds the comments for this post. comments.counterScriptCache.[usernum] caches the Javascript that generates comment counts when viewing Radio weblogs. I guess I want to basically take all the functions that generate the Javascript and make versions that do RSS like the comment monitor. 10:12:49 PM    comment [][Macro error: Can't call the script because the name "liveTopicsSuite" hasn't been defined.]