Re: Why streams?

Okay. Karl and Greg have certainly answered my question.

I suppose my thought was that once you have to bring an entire file in
anywhere, you already have a requirement for large virtual memory, and you
might as well leverage the convenience of memory mapping things. The size of
the tree as a whole is not (to my mind) terribly relevant, since all of the
operations of interest involve only one file at a time in the design I have
in mind (Yes, change sets are transacted. Using cryptographic names makes
this easy).

For shipping things over the net one certainly wants stream-like function
regardless. I was thinking mostly about the convenience of various internal
algorithms.

I shall have to think about the windowing issue for large delta generation.
Fortunately, the issue is confined to one part of the code.

Thanks again for indulging me in answers to naive questions.

shap
Received on Sat Oct 21 14:36:06 2006