When I've contrasted put() and update() I've been using the Hibernate cache terminology put() - cache fill (== putFromExternalRead()) - update - database change (== put()). I don't think a putFromExternalRead() would normally cause a "dirty read", but one possible interpretation of Scott's question was what would happen if you called putFromExternalRead() with data that wasn't yet committed to the database.
I don't know why the asynchronous replication of putFailFast() was added orginally, but my assumption is that it's about increasing concurrency and performance. Replicating cache fills synchronously doesn't increase correctness, so you might as well do it synchronously. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3977566#3977566 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3977566 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
