This is probably just a clarification, but I think this new behaviour wouldn't just apply on the VM where objects were first created. Any place a shared object migrates, its [local] transients will survive between a flush/fault cycle.
> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:tc-dev- > [EMAIL PROTECTED] On Behalf Of Orion Letizi > Sent: Tuesday, April 01, 2008 1:30 PM > To: [email protected] > Subject: Re: [tc-dev] I was thinking > > Sounds good to me. It'll be a lot less surprising for people who > don't expect their objects to disappear from the JVM they created it on. > > --Orion > > On Apr 1, 2008, at 1:23 PM, Steven Harris wrote: > > about transients. One thing we can do to simplify things a bit is to > > have a concept of a locally cached transient. What does this mean? > > This means that when a something is marked as a "Terracotta Transient" > > they can specify whether they want the transient to be saved > > to a cache on object flush and reinserted on object fault. > > > > We can extend the concept to make the "Transient Cache" to hold onto > > that object until it is DGC'd in the server. > > Any thoughts? > > > > _______________________________________________ > > tc-dev mailing list > > [email protected] > > http://lists.terracotta.org/mailman/listinfo/tc-dev > > _______________________________________________ > tc-dev mailing list > [email protected] > http://lists.terracotta.org/mailman/listinfo/tc-dev _______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
