Forum OpenACS Development: Response to BBoard development

Posted by Dan Wickstrom on
I would have to disagree. Having the bboard tied into the content repository has the potential for real benefits. The content repository provides the following:

  • Search interface
  • Versioning
  • Categorization
  • Common storage with other content and the ablity to add attributes to content.

I think searching is especially important, and having a common storage area for content, might make it easier to implement a search interface in postgresql. If we start tearing apart packages and implementing things like search on a ad-hoc basis, then we are really moving back towards the acs 3.x way of doing things.

It seems premature to throw out the content repository - especially since performance has not been proven to be an issue yet.

A better approach would be to do a straight port of the bboard package, and then evaluate the performance and decide if scaling and performance will be issues. Since openacs 4.x supports packages, an alternative might be to develop a bboard-lite package that doesn't depend on the content-repository or acs_objects.