Just another quick point: in addition to the features that have been implemented to support the Lotus Connections product, the IBM internal blogging environment team is developing a number of new features and general improvements that we will also be looking to add back to the roller base project. One of these is a new entry rating system and a "featured posts" query that will select featured posts based on cumulative rating, comment count, view count, etc. We're also looking to revamp the hit count tracking and add the ability to filter the aggregated list of entries by language/locale.
As Elias mentioned, we're in the process of securing all the legal approvals we need to donate this stuff back to the Roller project. - James Elias Torres wrote: > Hi Everyone, > > I know I have been away for over a month now but I still wanted to let > you know what we have been up to at IBM in regards to the Roller > project. First, we have some great news around the use of Roller at > IBM. Lotus announced Connections, a social networking package for the > enterprise that includes Roller as its blogging component. > > Now that the product code is stabilizing, we want to share with you > the things that we have done and added and plan how we can give these > back to the project. > > - New backend implementation using iBatis > - Reduction of # of sql queries to increase performance > - Better cluster support: > - MBeans implementation to support better administration in a > clustered environment > - Completely reworked search to work in clustered environment > and avoid re-indexing on improper shutdown > - Tweaked caching strategy to avoid blowin up the heap with output content > - Refactored code to have proper HTTP support for Reverse Proxies > - Cleaned up unnecessary creation of sessions > - Support for authenticated comments > - A lot of tweaks to support container managed security and SSO > environments > - For example, MetaWeblog API relied on passwords stored in the db > regardless of the setup > > I'm sure other things escape me, but I'll send more details as I > remember them. Anyways, we hadn't shared all of this publicly because > we are waiting for legal approval to share these code features back > with Roller as long as you are interested in approving the changes. > > I guess the main discussion point I would like to start from this > email is which data access strategy we should use in Roller. We have > an iBatis (Apache License) implementation that is working well and > continually being optimized. So far the results are very promising and > would like to donate that back. I just want to know if using iBatis > can still be a choice in the decision and what would need to do to > make sure it happens. > > Regards, > > -Elias >
