All; I have added a new section to the documentation, 'arch', for "Architecture". Currently it contains just my writings on the cache implementation but others are of course STRONGLY encouraged to contribute. This should not be API level stuff but design / architecture stuff that explores the concepts, designs, and interactions of components of ATS. I think it is also a good place for writing up design suggestions for future implementation.
In that vein, I have added a design Phil Sorber and I worked out at the ATS Summit in Denver concerning tiered storage in the cache. We think it's a reasonable level of implementation complexity while having a clean API, understandable semantics, a simple regression to the current implementation, and satisfying the requirements for people who want this. Unfortunately I will be out of town (without even guaranteed electrical power) until Thursday. I will probably only be able to check email once a day or so.
