On the other hand, as Henry suggests, it seems likely that there will be performance problems with the CR. All content revisions are stored in a single table regardless of whether they are live or not, so over time, the cr_revisions table could grow to be quite large, which could lead to performance problems.
That is why I suggested/prefer the "lite" approach. I don't think that versioning or adding attributes is needed for bboard and searching can be accomplished by implementing an interface with a method that provides the data to be indexed (Site Wide Search Design Document
). I think this is what the current bboard package does.
I don't want to sound like a curmudgeon or someone that is ungrateful for the considerable work the porters are
doing. Also, I think these suggestions are absolutely great. I just wonder whether it would be more effective to
consider these suggestions as feature requests that will be implemented for the next release.