What I noticed happening was "reads" of the session where resulting in
"saves" of the session data.  This caused problems when multiple async
requests coming from the same browser process, same session, when one
request modified the session, the other requests with slightly more stale
sessions could potentially overwrite "newer session data".

I think the setTimeout() here is not needed, the important part is the
check for "changed hash"....

-Dave


On Sun, Jan 13, 2013 at 1:54 PM, TJ Holowaychuk <notifications@github.com>wrote:

> encoding