Re: Can't modify EO objects! ARGH! =(
Re: Can't modify EO objects! ARGH! =(
- Subject: Re: Can't modify EO objects! ARGH! =(
- From: Jonathan Rochkind <email@hidden>
- Date: Mon, 21 Jul 2003 19:17:13 -0500
[Man, has Apple lowered the limit on maximum size of a message sent to the
list? I keep getting rejected for having a message that's too long. Oh
well, I guess I ought to be trimming the quoted text to be polite anyway.]
Another point I think of, as I'm currently dealing with it:
I think using PEER ECs instead of nested ECs is strongly to be encouraged,
unless you have a specific reason otherwise. Using nested ECs, you end up
doing something to your single session default EC, and if you do something
that somehow puts the EC in a corrupt state, that corrupt state is left
there for all subsequent uses, and will keep throwing exceptions. I'm
currently dealing with this.
Also, unfortunately, once you start using multiple ECs, you need to take
care of LOCKING them all. Doing this in a convenient and effective way is,
well, a pain in the ass. I'm currently working on a design for this, and
will share it once done.
Unfortunately, using multiple ECs makes your job as developer significantly
more complicated. But I don't know a good way to use EOF in a web
environment without multiple ECs. It's unavoidable.
--Jonathan
At 09:27 AM 7/22/2003 +1000, Marek Wawrzyczny wrote:
Thanks for the pointers, I'll have an in-depth look into multi-EC
strategies. Up until now I've simply had no need to use them.
Kind of reinforces the fact that with WO you never stop learning :)
On Tuesday, Jul 22, 2003, at 02:04 Australia/Sydney, Jonathan Rochkind
wrote:
There is an Apple document on using nested EC's to deal with exactly
the sort of thing we are talking about here. My current thinking
matches Chuck's on this though: it's probably better to use peer ECs
rather than nested ECs for this purpose. While the Apple document
reccomends nested ECs (wrongly, in my current opinion), the techniques
and code examples they give generally are right for peer ECs as well.
The only difference is in how you create the EC, naturally. [If you
DO choose to use nested ECs, the Apple document for some reason warns
you against 'doubly' nesting them. In fact, this warning is
unneccesary---you CAN doubly nest ECs, if you really mean to. But you
probably don't really mean to. And again, I think peer rather than
nested ECs are generally the way to go.]
Alas, the document doesn't exist in the current documentation. But
you can find it in the old documentation at:
http://developer.apple.com/documentation/WebObjects/WebObjects_5/
Topics/ProgrammingTopics.39.html
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.