Re: Q about locked ec
Re: Q about locked ec
- Subject: Re: Q about locked ec
- From: Steve Peery <email@hidden>
- Date: Thu, 18 Feb 2010 17:03:34 -0500
That could explain a few things.
Thanks, Steve
On Feb 18, 2010, at 4:20 PM, Anjo Krank wrote:
> A long response most of the time locks in start and unlocks on end. If you use the session EC for... well, you figure it out.
>
> Cheers, Anjo
>
>
>
> Am 18.02.2010 um 22:09 schrieb Steve Peery:
>
>> Does this apply to ERXLongResponse pages? I have a report that I moved to an ERXLongResponse page and now the app hangs occasionally. Could this be a locking issue?
>>
>> Thanks, Steve
>>
>>
>> On Feb 17, 2010, at 5:21 PM, Anjo Krank wrote:
>>
>>> You *can* pass EOs between threads. You just really, wanna make sure your threads don't block each other (and do proper locking, auto may not be good enough). In particular, you don't wanna use the session EC in a long running thread.
>>>
>>> Cheers, Anjo
>>>
>>>
>>>
>>> Am 17.02.2010 um 21:23 schrieb Kieran Kelleher:
>>>
>>>> 1) Don't pass EOs between threads. Pass their EOGlobalIDs and use ec.faultForGlobalID to rehydrate them in an ec in the thread that needs them. Use Wonder ERXEO<Something>Utilities.convertEOtoGID if desired. (Something = 'Access' or 'Control', I can never remember which)
>>>>
>>>
>>> _______________________________________________
>>> Do not post admin requests to the list. They will be ignored.
>>> Webobjects-dev mailing list (email@hidden)
>>> Help/Unsubscribe/Update your Subscription:
>>>
>>> This email sent to email@hidden
>>
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden