Right. Apparently I just used poorly chosen wording. What I meant to say is that it is "conceptually" what TopLink achieves with its separation of Session and UnitOfWork. As Gavin pointed out in his response, sharing actual instances between sessions and/or threads is not desirable. That was not my intent to imply such a thing.
-----Original Message----- From: Joshua Davis [mailto:[EMAIL PROTECTED] Sent: Monday, January 03, 2005 10:18 PM To: Steve Ebersole Cc: Max Andersen; Hibernate development Subject: Re: [Hibernate] someone looking at flushing performance... Steve Ebersole wrote: >[...snip...] Then we could continue to track these >objects within the scope of object identity but not in the session cache >(aka, this is analogous to TopLink's distinction between Session and >UnitOfWork). > > ... except better than TopLink. The TOPLink Session stores objects that are used by multiple threads, which introduces a lot of problems that nobody needs to have. > >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On Behalf Of Max >Rydahl Andersen >Sent: Sunday, December 26, 2004 1:53 PM >To: Hibernate development >Subject: [Hibernate] someone looking at flushing performance... > >...fyi: http://forum.hibernate.org/viewtopic.php?t=936291 > >Is he on to something or is the readonly stuff in H3 the answer to this >? > > > ------------------------------------------------------- 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 _______________________________________________ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
