When to use the new file based content repository

Question

In Service Pack 4 there's a new implementation of the CMSPI interfaces which is configured by using the following implementation class:
com.bea.content.spi.internal.FileSystemRepositoryImpl
When should one use this new file based repository versus the existing one (configured by using the following class: com.bea.content.spi.internal.RepositoryImpl).
I've read the edocs, but it doesn't state when to use this new one compared to the previous implementation.
We consider using a third party content repository, but for the time being we will use the content repository provided by BEA.
Trond Andersen, Invenia AS, [phone]

Answer 1

use the new keyword when you don't have an instance of that object in memory that you want to use.  For example...
if you have an object already in memory that is holding a property with a "CamelQuery" object, then you can say 
var query = myobject.Query;
however, if you have to write the query, or instantiate the object from nothing, then you need to use the "new" keyword.  A good example is SPSite object...
if you can get a new SPSite object by either "newing one up and passing the URL" or getting the farm and getting a site from that object. 
using(SPSite site = new SPSite("url to my site"))
now I can use site.
//or
SPSite = myWebApp.Sites[0];
// this gives you site at index 0 of current webApp
most of the time in SharePOint you will be using the "new" keyword to open site collections, and then getting your subsites from there. BE CAREFUL using the "new" keyword. If you "new" up an object that is iDisposable... you
MUST dispose of that, but if you use that same object but it comes from the "current context", you mustn't dispose of it.
//dispose of this by using statement
using(SPSite site = new SPSite(<url>))
//do stuff
//after this bracket it is disposed.
//do not dispose of this:
SPSite mysite = SPContext.Current.Site;
//unpredictable behavior can occur because you will still need references to your current site.