4 ms·
Part 2 drives me crazy. http://news.ycombinator.com/item?id=151663 http://news.ycombinator.com/item?id=151663
by j2d2 18y ago
Part 2 drives me crazy.
http://news.ycombinator.com/item?id=151663 http://news.ycombinator.com/item?id=151663
- joshwa 18y agohttp://news.ycombinator.com/item?id=163696 http://news.ycombinator.com/item?id=163696
- SirWart 18y agoI haven't looked that closely at arc, but if it's a continuation based web server (for some reason I thought it was) it has to store those continuations on the server, which means it has to get rid of them after a certain timeout period. Considering I get that expired message quite a bit, I suppose the timeout isn't long enough. On the plus side, because I have to go back, about half the time I go back I see someone has said something similar to what I was going to say but clearer and more succinctly, which means I don't have to bother posting whatever I was writing.
- axod 18y agoThat sounds understandable technically, but if there has to be a timeout, perhaps continuations aren't a great idea for this sort of thing.
- subwindow 18y agoAgreed. Any time you type a comment longer than a paragraph or two, you get that message. This seems like a fundamental shortcoming of the continuation-based request approach. POST URLs should never expire.
- stcredzero 18y agoThat happened when I answered pg once. I always thought he just erased my comment because he thought I was a redundant cheesehead.
- pg 18y agoThis seems like a fundamental shortcoming of the continuation-based request approach. Nope. You just add times to the closures.
- cstejerean 18y agoI created a poll http://news.ycombinator.com/item?id=196196 http://news.ycombinator.com/item?id=196196 with some of this issues, I'd like to see how many people care about each one and maybe we can convince PG to start fixing some of them (or release updated source code and accept patches)