Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Unfortunately if you are sending the friend list as part of the cached page then you won't be able to use that cached page for all users.

I believe the original comment was that each comments page should be cached globally and then each user can have their friend list & dynamic data fetched separately and added to the page using javascript.



You could if using SSI (say, with nginx or varnish).

<html> <cached comments here> <!ssi include="/load-json" /> </html>


Ah, my bad then. I don't think the comments pages cache well though--the votes are always going up and down. My understanding that in addition to pulling all the comments for each request they were also pulling the friend relationships for the current user with all the participants.


Who cares if the votes are say 1 minute out of date?

Even caching a 2000 comment thread for a minute would significantly speed up that page.


I think it would be confusing to post a comment and have it disappear after a refresh. Same for votes.


The page would be regenerated on each new comment, of course.

Votes should be done the same way friends' lists are: on the client side, via javascript. The cached page with its comments would include Javascript to grab the most current scores for all its posts (one request) and modify the DOM appropriately.


The comments page would be cached globally; the json friends list would just be inserted as the cached page is served to the user.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: