Geoff Howard <[EMAIL PROTECTED]> writes: > > Umm why? You can still invalidate the validity in any > manner you see > > appropriate, or for that matter, you can still manage the cache of > > actual data in any way you see fit... > > I may have been jumping to conclusions, but my assumption > based on the > overall discussion was that to make forced caching easier > that most of > the Impl components would have a validity provided. For instance the > discussion on the added complexity of configuring my > solution. I could > be misunderstanding here, though?
Hmm, I can see if this wasn't done carefully that it would cause problems. However, I'd assume that any event driven component would override any default validity? > Good point on the sensitive data issue - I assume your work > has similar > requirements? (from what I remember) Well sort of; we don't currently care about any memory based cache, but persistent cache might be an issue. We assume a secure server environment...
