The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 |
From: "Sean Corfield" <seancorfi...@gmail.com>
Date: Sun, 11 May 2008 09:22:26 -0700
Local: Sun, May 11 2008 12:22 pm
Subject: Re: [transfer-dev] Re: Transfer objects in session scope and reiniting application
On Sat, May 10, 2008 at 6:55 PM, Brian Kotek <brian...@gmail.com> wrote: Are you saying you add information to the User object but don't commit > I'm trying to figure out a workaround for this, since I do have a User > object that I want to keep in the session scope. The basic solution of just > keeping the ID and calling Transfer.get() each time isn't a good choice for > me, since I have other instance data that is built up and kept in the User > object that would be lost if the object falls out of cache and > Transfer.get() actually returns a new instance. it? That sounds like a poor design to me. Transfer objects are meant to be persistent objects - if you modify the User object in memory, it will affect *all* uses of that object (by other threads) since there is only one cached object (by default). If I understand correctly what you're doing, you're just setting yourself up for data corruption and all sorts of hard-to-debug problems. > To be honest, I'm still not How would Transfer know where you stored the reference? If Transfer > clear at all on how a session-scoped TO could fall out of cache > anyway...isn't the fact that it is in the session scope creating a > continuous strong reference to that object? Is this some kind of bug in CF's > session handling? needs to reap its cache and that User object is a candidates based on its usage pattern, out it goes. Your session scope reference is completely independent of what Transfer knows about. -- Sean A Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ "If you're not annoying somebody, you're not really alive." You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
| |||||||||||||