Daniel John Debrunner wrote:
Jeremy Boynes wrote:
If we rush a release out now and unify later, users see:
10.1 new ClientDataSource and EmbeddedSimpleDataSource
10.x new DerbyDataSource, deprecation of Client, EmbeddedSimple
and Embedded
If x = 1.1 or 2 then what we did in 10.1 looks silly and, because it is
a public API, we live with it forever (or a couple of years at least).
I don't see it as silly, but the unified datasource being an feature
that might obsolete the other data sources.
If the others existed already then fine - but they are new this release
so its a feature being obsoleted almost immediately.
This approach is a great
chance for the open source Darwin approach, see what the users like,
see how much confusion (e.g. questions in derby-user) there is with a
single data source with all properties vs. multiple data sources with
specific properties.
Should I roll it into the main tree then? Then we can have both there in
the alpha/beta versions and get can feedback from users early.
--
Jeremy
