Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 64342 invoked from network); 12 Feb 2008 20:03:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Feb 2008 20:03:28 -0000 Received: (qmail 57062 invoked by uid 500); 12 Feb 2008 20:03:20 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 57042 invoked by uid 500); 12 Feb 2008 20:03:20 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 57033 invoked by uid 99); 12 Feb 2008 20:03:20 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Feb 2008 12:03:20 -0800 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [213.86.32.131] (HELO mobile.synchronica.com) (213.86.32.131) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 12 Feb 2008 20:02:47 +0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4133 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C86DB2.4CFE5670" Subject: RE: Repository factory, was: SPI caching, was: [jira] Resolved:(JCR-1361) Lock testassumesthat changes in one session are immediatelyvisible in differentsession Date: Tue, 12 Feb 2008 20:03:14 -0000 Message-ID: Content-Transfer-Encoding: 7bit X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Repository factory, was: SPI caching, was: [jira] Resolved:(JCR-1361) Lock testassumesthat changes in one session are immediatelyvisible in differentsession Thread-Index: AchtsWqMWFZC5PmmQU+c5N9SUZCjTA== References: <10340167.1202296988432.JavaMail.jira@brutus><47A9A975.70701@gmx.de> <47A9D3EE.5000108@day.com> <47A9D69B.60806@gmx.de><47AABD1C.5020500@gmx.net> <47AAE7B4.4070803@gmx.de><47AAFD83.1090001@gmx.net> <47AB02BD.20500@gmx.de><47B08A91.2080604@gmx.de> <1202817113.10574.15.camel@davidr-laptop><1202820893.10574.27.camel@davidr-laptop> <47B19AE3.5070100@gmx.de> <1202827806.10574.40.camel@davidr-laptop> From: "David Rauschenbach" Importance: normal To: "David Rauschenbach" , Priority: normal X-Virus-Checked: Checked by ClamAV on apache.org ------_=_NextPart_001_01C86DB2.4CFE5670 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable =A0 Another one of the areas with potential for performance improvement is = in JCR2SPI. Sometimes fetching a node will cause getItemInfos to be = called, which can return all the properties for a node at once, which is = great. But other times, the JCR client calling code might access 8 = properties, and it results in 8 separate getPropertyInfo calls instead = of a single getItemInfos call. That is one area where I am trying to put = adaptive code into my SPI's, to intercept the getPropertyInfo at some = point and invoke getItemInfos instead. I don't know what, if any of = this, could end up in JCR2SPI as a generalized solution, but I'll be = keeping it in mind. David -----Original Message----- From: David Rauschenbach Sent: Tue 2/12/2008 3:50 PM To: dev@jackrabbit.apache.org Subject: Re: Repository factory, was: SPI caching, was: [jira] = Resolved:(JCR-1361) Lock testassumesthat changes in one session are = immediatelyvisible in differentsession =20 Yes I use a custom RepositoryConfig, and implement bean methods there for custom configuration, as it applies to whatever the repository is. But, there's no way to remote a serialized RepositoryConfig over SPI, to do the factory work at the remote end, if you know what I mean. Again, just because the spec doesn't address how to do the configuration and factory work doesn't mean it doesn't have to happen. That's where some flexibility in SPI is needed, so that it can allow someone to write a proxy, or gateway, or middleware of whatever sort. Sorry I was not clear about the repository descriptors. Yes you're right you can ask for descriptors without credentials, but that's the same reason you could never make that call to an SPI web service that used container-managed security, to get those descriptors, because during such a call the credentials are not yet known. This could be fudged, if it were not for the fact that JCR2SPI asks for the descriptors before attempting a login, even though I seem to recall examining the code and seeing it had no pressing need for those descriptors until after login, when nodes were being dealt with. David =A0 Visit Synchronica at GSMA Mobile World Congress, Barcelona, 11-14 Feb, = Hall 2, Booth #2J25 =A0 =A0 ------_=_NextPart_001_01C86DB2.4CFE5670--