Here is what's bugging me. An editing context is part of a session.
Many of Apple's diagrams indicate so clearly. I'm aware of the
model/view/controller paradigm but I don't see any intrinsic reason
the editing context shouldn't have a method to return the session
object. What the heck am I missing?
Why should an editing context require a session? There are plenty of
applications that could use EOF that have nothing to do with a session
or anything like one. Then there's DirectActions and their need for
editing contexts, too. And what about things like javaeoutil?
----
WO in philadelphia - wanna cheesesteak with that?
Please visit webobjects.meetup.com.
_______________________________________________
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.
