Re: Separate EO Models
Re: Separate EO Models
- Subject: Re: Separate EO Models
- From: Colin Clark <email@hidden>
- Date: Wed, 21 Jul 2004 11:49:35 -0400
Hi Ryan,
I expect that the reason for multiple models--at least in the case of
Ravi Mendis' tutorial--is to facilitate reuse. Presumably his user
account design is applicable to more than just the forums application.
In terms of design, if a portion of your schema is reused across a
number of applications, it is probably a benefit to separate that
portion into its own model. At that point, you'd likely create a
framework to encapsulate the model and your own custom logic for reuse
across multiple application, unencumbered by the application-specific
model material.
Does that answer your question?
Colin
On Tuesday, July 20, 2004, at 08:38 PM, Lotsa Cabo wrote:
Looking back on some of the tutorials I've worked through, virtually
all of them have the reader creating multiple EO models for each
WebObjects application. For example, one for "Forums" and one for
"Users" (from Ravi Mendi's book). Is there a benefit to this or is it
just some coincidence where the authors are attempting to make an
easier read?
Thanx,
Ryan
"I'm a newbie... she's a newbie... wouldn't you like to be a noobie
too?"
_________________________
Tired of spam? Signup for a FREE SpamJammer.Com account and say
goodbye to junk email forever!
_______________________________________________
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.
---
Colin Clark
Dynamic Web and Database Development Lead,
Resource Centre for Academic Technology,
University of Toronto
(416) 946-7592 / email@hidden
_______________________________________________
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.