Hi jukka
Jukka Zitting wrote:
Hi,
Edgar Poce wrote:
But I like to use jndi, so IMHO the ClientRepositoryFactory should
validate the reference to the remote repository and discard the cached
references when they become stale, just like a jdbc pool discards
stale connections. thoughts?
Now that I think about this, I'm not sure why I decided to introduce the
connection cache in the ClientRepositoryFactory. There doesn't seem to
be any great benefit in caching the connections (at this level) and the
current behaviour only introduces unnecessary complexity. Would anyone
mind if I just removed the connection cache to solve this issue?
I think it's ok.
btw, I've just committed a command to jcr-command that connects to a
remote repository through jcr-rmi, so you can benchmark jcr-rmi and use
it with the command line interface.
br,
edgar
If needed, connections could still be cached for example by using JNDI
or some other solution like commons-pool.
BR,
Jukka Zitting
