> How can we guarantee ids are unique *and* sequential in a > cluster without (too much) overhead?
use the path as id instead of generating some arbitrary id? after all, most methods of the JCR API operate on a path and not an id. regards marcel
> How can we guarantee ids are unique *and* sequential in a > cluster without (too much) overhead?
use the path as id instead of generating some arbitrary id? after all, most methods of the JCR API operate on a path and not an id. regards marcel