hi oliver, > (1) Where can I get the (tentative) JCR API? you can download the snapshot that was out for public review in may-2004 ( http://jcp.org/aboutJava/communityprocess/review/jsr170/index.html ) which is a quite a bit outdated now. or you can get the binaries that are used by maven to build for jackrabbit from http://www.day.com/maven/ "proposed final draft" will be submitted soon (i hope).
i think you bring up a good point, we should somehow manage to get the java-doc of the jsr-170 into the jackrabbit api doc. > (2) When *presumably* will Jackrabbit be mature enought > to be an alternative to the current Slide backend? since i do not know slide well enough to understand how mature it is and i cannot judge what it would mean to be an alternative to the slide backend, i can only speak for jackrabbit. even when jackrabbit was still a slide proposal people (unfortuntately) started to use it in production. there are already mature applications that are built uniquely on jackrabbit, so far people have been very happy with the stability. i am sure there are very different mechanisms to measure robustness, which are usually very dependant on the requirements of the users. do you have any sort of performance metrics in mind? uptime? size of the repository in bytes or nodes (resources)? transactions per second? functionality (versioning, query, transactions,...?)? memory consumption? if there are any standard loadtests that are used for slide i am sure we could port them over to jsr-170 and see how jackrabbit compares today... (which as a side effect would allow us to have the worlds first "general purpose content repository benchmark" that would run against any jsr-170 compliant repository ;) ) david --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
