I completely agree with that approach (TDD). I think examining how systems like hibernate and toplink handle session/connection relationships would point us in the right direction. Since jackrabbit is seen as something embedded within the servlet container using an embedded db I see the reason for doing a connection per workspace, however, once data grows to a certain point or the db becomes remote I have a feeling that it would be advantageous to allow each worker thread independent access to the repository. This would mean, however, leveraging or creating a more complex transactional framework and dealing with pooling, etc.

-paddy

Reply via email to