However, you need to manually lock/unlock your ecs used in Long
responses... and it's probably not a good idea using the session's
ec in your long response.
You can extend ERXWOLongResponsePage to get similar autolocking
behavior that you would in a normal RR-loop, btw. And actually even
in a regular long response, you'll get autolocking, but not coalesced
locks (ERXWOLongRP adds that specifically). But definitely I agree
that using session EC's and EO's that came from session EC's in a long
response page is a really bad idea. Actually, passing EO's across
thread boundaries _in general_ is a bit of a tricky thing to lock
properly. I often bypass this problem completely and pass GID's
across thread boundaries rather than EO's.
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
