On 1/2/07, Thilo Goetz <[EMAIL PROTECTED]> wrote:
I wouldn't mind doing this as a first step, but I'm concerned about the
future.  If we need to support this approach going forward, I would
prefer if we could answer the questions about the relation between the
CAS and CasViews first: how are indexes in the CAS related to indexes in
  CasViews?  If we're ok with maybe changing this again in the next
release, I'm ok with starting like this.


This proposal only has indexed in CasViews, not indexes that belong
directly to the CAS. (Unless you meant the deprecated index-access
methods on CAS that use the current view.)

I would also like to figure out if there should be such a thing as
indexes that belong directly to the CAS ("global" indexes?), but it
seemed like we were too far from a consensus on that to get anything
done for 2.1.

We can always add additional methods to CAS (i.e.
getGlobalIndexRepository()) in a later version if we decide that's
right.  And we probably can't redefine any of the existing indexing
methods on CAS without breaking a lot of code anyway.  So it "smells"
like starting with this proposal will not get in the way of future
enhancements.

-Adam

Reply via email to