Ben,
I'm happy for you to move this thread to the design forum. I saw it there, but 
it looks, well, very under-used :-)

As for your suggestion, I'm not sure that it'll do what I'm thinking. Sending 
an event on a field r/w is probably too limiting. Realistically I'm after a 
single user-defined event per transaction. Actually, it could be multiple 
events per transaction, but the idea is still the same.

I guess what I really want to do is be able to push around a user-defined bit 
of data within the cache transaction. If I do it outside of the cache (say 
using JGroups directly) then I end up with potential race conditions with 
events being received out of order etc. I need the guarantee that the 
transaction provides.

Any thoughts? Do you think this change (or something like it anyway) is 
reasonable?

Tim.

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3863331#3863331

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3863331


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
JBoss-Development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to