It depends on what your use case is. You can manually do whatever makes sense for you (and it will lock for you regardless), but in general, we can't really just do this in any easy way. In most cases a component gets passed in an EO or an array of EOs, and you don't know what EC it originally came from, so you sort of have to solve this in the general case. For instance, I use peer editing contexts a lot on pages where i fetch big sets of data almost like a peer NSAutoreleasePool, so I can dispose the EC and clean up the entire lot. If everything is loaded in session, it's hard to do things like that.
ms
On May 31, 2007, at 1:42 PM, Ted Archibald wrote: In this instance, couldn't you have all the EOs you're using in the defaultEC then just transfer them into ERXEC via localInstancesOfObjects?
On 5/31/07, Mike Schrag <email@hidden> wrote:
2) Closely related to that, it's very common to do a bunch of things in close succession. Think of rendering a page. You bind to all sorts of EO's, and every operation that touches EO's potentially needs a lock. If you were to turn on lock debugging, you'd see that Wonder is going to go locking and unlocking your EC. It's really just spending a lot of time doing things that it doesn't need to, and stack on top of that #1, that you really generally don't WANT sparse locking, and you get a recipe for obnoxious lock behavior.
_______________________________________________ Do not post admin requests to the list. They will be ignored. Help/Unsubscribe/Update your Subscription:
|
