On Fri, Jan 9, 2009 at 8:59 AM, Angela Schreiber <[email protected]> wrote:
>> - using the SPI interface, which is kind of a "batch-optimized" and
>> smaller API compared to JCR, but provides the same feature set
>
> just for clarification: the SPI is an internal layer
> and not meant to be used *instead* of the JCR API.

Oh, yes, you are right, sorry for any confusion.

It is very useful in the long run to stick with the JCR API and not
use workarounds (like direct access to the files in the datastore,
accessing the db directly, using a "similar" API like SPI, etc.),
because JCR is a good standard and it keeps your source independent
from the application.

Regards,
Alex

-- 
Alexander Klimetschek
[email protected]

Reply via email to