*Which* Newest Nodes node? Your "newest nodes since" flag isn't the same as mine.

ummm... huh! that was pretty stupid of me :)

but the idea is still salvageble. we're aiming for the common case - extream cases can default and still go hit the DB, after missing the cache.

what I'm thinking of is have an incremental cache, starting with the latest post, and going back, up to a day back. Then, when a client is asking for "show me the newest nodes in the last 10 mintues", the cache process just scans the flat file on the webserver, stopping when it is father back than 10 minutes, and shows the collected data. Of course, if it reaches the end of the cache, and still doesn't reach far enough back, then it just defaults to the current behaviour. Performance hit to that user, but that's the rare case.

sample data could look like this:

1044638805|sopw|How do I download a file?|Anonimous Monk
1044638800|sopw|How do I get my script to run?|Newbie
1044638523|med|Pondering the meaning of perl|Phil
...
[download]

yes, the cache process would put some load on the web servers, but from what I understand we can afford that load, and it would defenitly reduce the load on the database, because the cache would only have to be updated once in a while

does this make any more sense now?

-- zigdon