On 8/13/06, Jon Smirl <jonsmirl / gmail.com> wrote:
> Active sessions would stay as files and generate a new key each time
> they are changed. Once a day you would sweep them into a pack. You
> will need to make some small modifications for the git code to do this
> but all of the hard code is already written.
>
> With git's compression you will be able to store hundreds of millions
> of session snapshots in a couple of gigs of disk.  It would provide
> interesting data for later analysis.


Once again, you're solving a rather different problem (or perhaps
you're redefining the problem to fit your solution): permanently
storing ephemeral session caches for later analysis is interesting but
different from just having a session cache that survives process
crashes. Yes, the "hard work" is done, but if you didn't need to do
the hard work in the first place, it's wasteful. Again, this whole
subthread is about Kirk's filesystem approach, which is attractive for
some applications (not including yours) because it's dead easy and it
may be "fast enough."