[ http://jira.jboss.com/jira/browse/JBCACHE-4?page=history ] Bela Ban resolved JBCACHE-4: ----------------------------
Resolution: Rejected Ben has another way of doing this in session repl, no need for it > Notification of remote modification > ----------------------------------- > > Key: JBCACHE-4 > URL: http://jira.jboss.com/jira/browse/JBCACHE-4 > Project: JBoss Cache > Type: Task > Versions: 1.3 > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 1.3 > > Original Estimate: 1 week > Remaining: 1 week > > TreeCache need to emit a node event that is modify by remote > only, i.e., local modification won't trigger this event. > This event is needed to listen for remote modification when > there is a local copy of this instance around so we know that > it is dirty. Use cases are: http session repl and TreeCacheAop > where after getObject will need a way to know if the underlying > fields have been modified remotely. -- 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 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development