[ http://jira.jboss.com/jira/browse/JBCACHE-118?page=history ]
Bela Ban updated JBCACHE-118:
-----------------------------
Fix Version: 1.2.4
(was: 1.2.3)
> Inefficient CacheLoader.exists() followed by CacheLoader.get()
> --------------------------------------------------------------
>
> Key: JBCACHE-118
> URL: http://jira.jboss.com/jira/browse/JBCACHE-118
> Project: JBoss Cache
> Type: Task
> Versions: 1.2.1
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 1.2.4
>
>
> I have a CacheLoader that I am using to allow a TreeCache to act as the
> primary interface to a DAV/JDBC data model. Each access to the backend can be
> quite expensive. I note that a CacheLoader.get() is always preceeded by a
> CacheLoader.exists(), which seems redundant to me and has the unfortunate
> effect of doubling the backend load. Am I missing something here?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
This SF.net email is sponsored by Demarc:
A global provider of Threat Management Solutions.
Download our HomeAdmin security software for free today!
http://www.demarc.com/info/Sentarus/hamr30
_______________________________________________
JBoss-Development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-development
