Adam Lally wrote:
On 12/13/06, Thilo Goetz <[EMAIL PROTECTED]> wrote:
...
I can only restate what I said earlier: to my
mind, conceptual clarity of the APIs is more important than backward
compatility.
Well we probably have to answer this question of philosophy before we
can make technical progress. I'm unwilling to make such an
unconditional statement. I think backward compatibility is very
important, and that we should seriously consider the option of
deprecating things rather than removing them.
Let's disregard the question of backward compatibility for a moment. In
an ideal world, where we could design the APIs the way we wanted, what
would we do?
My suggestion would be to completely separate the base CAS and CASView
APIs, as Marshall also suggested in an earlier note. I see no reason to
have the FS creation APIs on the base CAS. From a user's perspective,
FSs are always particular to a view since they can only be index wrt a
view, and retrieved wrt to a view. So why should they be created on a
base CAS? The only thing the base CAS should be concerned with then is
the administration of views.
--Thilo
