4 ms·
I believe it's a continuation-style server—hence fnid: function id—and the continuations are only kept around in memory for ~5 minutes.
by kalmar 13y ago
I believe it's a continuation-style server—hence fnid: function id—and the continuations are only kept around in memory for ~5 minutes.
- lucian1900 13y agoI never understood why the continuation couldn't instead be addressed by a URL path. It could even get constructed from URL/query data if it moves out of memory, so keeping them in memory would only be a caching mechanism.
- pfarrell 13y agoYes, but the way hn works, the continuations map uri's to browser sessions so they can be expired on a more granular basis than all at once or lru or what have you. I'm guessing here, though, I've not looked through the code. [addendum] I Reread your comment and realized that wasn't what you meant at all. What would be the benefit of path based uris over query string params in hn's case? I only see how they be equal, not better.
- lucian1900 13y agoI meant that the continuation could be identified by (session_id, URL data), and re-created based on this data if it goes missing. URL data can come from path or query string, it doesn't matter.
- acdha 13y agoEvery continuation framework I've looked at radiates an intense desire to treat the web as something other than what it actually is.