These error messages are a consequence of any scheme that stores session state on the server: the session data must expire, or the server will fill up. The problem would remain even if some other method of serialization was used instead of continuations.
That said, I expect that continuations store more data than a hand-tuned serialization and thus need to be expired earlier. I'd be curious to know how much more space is used storing continuations versus the bare minimum.
Some sort of stateless method of interacting with a site helps alleviate the session problem. That's one of the touted advantages of REST architecture.
Comments
And no one ever tells us the drawbacks of continuations...
(Why is this so?)
These error messages are a consequence of any scheme that stores session state on the server: the session data must expire, or the server will fill up. The problem would remain even if some other method of serialization was used instead of continuations.
That said, I expect that continuations store more data than a hand-tuned serialization and thus need to be expired earlier. I'd be curious to know how much more space is used storing continuations versus the bare minimum.
Some sort of stateless method of interacting with a site helps alleviate the session problem. That's one of the touted advantages of REST architecture.