<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br></div><div><br>On Mar 3, 2016, at 11:21 AM, Bert Freudenberg <<a href="mailto:bert@freudenbergs.de">bert@freudenbergs.de</a>> wrote:<br><br></div><blockquote type="cite"><div><span><a href="https://news.ycombinator.com/item?id=11212732">https://news.ycombinator.com/item?id=11212732</a></span><br></div></blockquote><br><div>Interesting:</div><div><table border="0" style="font-family: Verdana, Geneva, sans-serif;"><tbody><tr><td class="ind" style="height: inherit !important;"><font face="UICTFontTextStyleBody"><span style="background-color: rgba(255, 255, 255, 0);"><img src="https://news.ycombinator.com/s.gif" height="1" width="80" style="width: 24px;"></span></font></td><td valign="top" class="votelinks" style="min-width: 18px; height: inherit !important;"><center><a id="up_11216194" href="https://news.ycombinator.com/vote?for=11216194&dir=up&goto=item%3Fid%3D11212732" style="text-decoration: none; display: block; margin-bottom: 9px;"><div class="votearrow" title="upvote" style="width: 10px; height: 10px; border: 0px; margin: 3px 6px 6px 2px; background-image: url(https://news.ycombinator.com/grayarrow2x.gif); background-size: 10px; transform: scale(1.3, 1.3); background-position: initial initial; background-repeat: no-repeat no-repeat;"></div></a></center></td><td class="default" style="height: inherit !important;"><div style="margin-top: 2px; margin-bottom: -10px;"><br></div><font face="UICTFontTextStyleBody"><span style="background-color: rgba(255, 255, 255, 0);"><br><span class="comment"><span class="c00">Not just way back; HN uses continuations. (Not in many user-visible places any more, but every link on the front page used to be one—expired "next page" continuation links were a frequent source of grumbling.)<p style="margin-top: 8px; margin-bottom: 0px;">Note that you don't have to expire continuations, necessarily—you could actually persist them statelessly (i.e. without server-side state), by shipping their encoded representations <i>to the client</i> embedded into HMAC-signed links. You're basically giving the server a raw bytecode-eval endpoint, and then making sure that it only accepts code you yourself wrote. Kind of a crazy strategy compared to the standard predeclared REST API, but interestingly flexible.</p></span></span></span></font></td></tr></tbody></table></div></body></html>