On 9/8/07, Ryan Holmes <[EMAIL PROTECTED]> wrote: > Is it not recommended because the new disk-based session store is > just a better all-around solution or because using the > httpsessionstore is dangerous or broken in some way in 1.3?
It is a better all-round solution: it is more efficient memory wise, and the cost of serializing and saving is neglect-able in our experience (like 1 or 2 miliseconds per request even without Matej's recent optimizations). HttpSessionStore (in 1.3, but also in 1.2) suffers from some limitations that the SLCSS doesn't have. Particularly, back button history is limited, and while we don't experience many real problems with it, we feel that recording change objects isn't as robust as just serializing the page exactly as it is. It sounds way more efficient to do just the change objects, but compared to just serializing the page, it hardly seems to be in practice. Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
