Re: Design Question
Re: Design Question
- Subject: Re: Design Question
- From: Chuck Hill <email@hidden>
- Date: Thu, 22 Jul 2004 14:30:35 -0700
On Jul 22, 2004, at 1:56 PM, James Cicenia wrote:
Hello -
Due to the nature of a very intense deadline I created my first
WebObject
application and it rocks! Thanks again to all that have ever helped me.
Now, as I go back through my code I start to think... is this really
the WO Way?
Here is my question... My pages/components are comprised of nested sub
components.
Originally, I had put all my query logic within these components.
Erk! That's hideous!
Now I wonder, where is the best place to put this logic?
Not where it is. :-)
Should it be in my own EO class?
Probably. Or in a higher level work flow or business process object.
This would be ok, I think, for
some of the logic... for this portfolio give me a sorted list of
projects. Now this seems ok, because
I will only have one portfolio in memory per session at a time.
However, what about the project
classes? There will be many in memory at one time, so would no
necessarily want any query
logic there.
Um, why not? What possible difference would that make?
Should there be some other "shadow" type class to do all the queries?
Should these
classes be instantiated at the Application level?
I'm rather unclear on what your concerns are. Logic in Java code does
not consume memory on a per object basis. It it per class.
Chuck
_______________________________________________
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.