rob wrote:
All,
we are currently working on various enhancements to Roller internally at
IBM. One of the things we have completed is a persistence layer built
on iBatis (iBatis has an apache license)
We have it functionally complete and tested in mysql, db2 and oracle.
We are committed to stabilizing the persistence layer further as we
still have to put it through further testing including a complete
performance test and rolling it out to the internal blogging community
at IBM.
We are willing to make this available to the community if it is of
interest and have secured management approval to do so. It was written
by myself and another developer here at IBM and we are in the process of
winding our way through the various legal processes here at IBM so that
we can sign a CLA.
Please let me know if this is of interest to you,
I think that people would be interested in this, but a very important
question would be how to contribute it to the project. To answer that
question we would really need to have a full discussion about how the
persistence layer is going to be managed going forward, which is
something that I think is somewhat unresolved at this point.
Generally speaking, I think that the approach for Roller should be to
pick a single persistence implementation to to be the official one
supported by the project and let any alternatives be managed
independently. I don't think there is any problem with having those
alternatives be managed in the same code base, but I wouldn't include
them in a normal build or distribution, they would have to be addons.
-- Allen
Thanks,
Rob
