jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Rauschenbach" <David.Rauschenb...@SYNCHRONICA.COM>
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 GMT
 
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
 
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

 
Visit Synchronica at GSMA Mobile World Congress, Barcelona, 11-14 Feb, Hall 2, Booth #2J25
 
 

Mime
  • Unnamed multipart/alternative (inline, 7-Bit, 0 bytes)
View raw message