LOL, this is essentially exactly what I proposed with the JBossCache folks for efficient clustering. One additional thing though that I proposed was the ability to explicitly specify when to clear the collected changeset and re-collecting.
-----Original Message----- From: Gavin King Sent: Saturday, September 23, 2006 8:27 AM To: Steve Ebersole Cc: hibernate-devel@lists.sourceforge.net Subject: new SPI for EJB3/Seam For truly efficient clustering of extended persistence contexts in the context of Seam or EJB3, we need a way to propagate unflushed changesets. What we need is an SPI like this: Serializable changeset = session1.getChangeSet(); session2.applyChangeSet(changeset); where session2 is an empty session, or perhaps even a session with some of the same entities as session1. The only state that needs to be sent in the changeset is new entities, unflushed updates to entities and deletions of entities. Steve, WDYT? _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
