Object Oriented Overkill ?

[sonoflight]

Hello all, I'm curious about my current development methods with CFMX 6+ and
your opinions. I wonder if it is possible to go too far with "objectifying"
things in Coldfusion. Take this simple example.

An application keeps track of current events in a database. I create a
component / class that represents an Event with all its methods like getTime(),
getDate(), and getDescription(). Now I create another component / class, an
EventSchedule. Whenever I need to get a list of all Events, I would create an
EventSchedule object and execute its method getAllClasses(). Now, the
EventSchedule method, getAllClasses(), returns an array of Event objects.
These objects were "filled" with their data using a query, looping through the
query and adding all the Event data. Now the page that needs a list of all
Events would create an EventSchedule object, call the method getAllEvents(),
and then the page would receive an array of Event objects for use. Thus being
able to loop through the array and calling the appropriate methods of each
object.

Is this overkill in object oriented design for ColdFusion? From a performance
/ execution standpoint? Anything I should consider or be worried about with
this methodology shown above? I know performance-wise, the server seems to be
taking somewhat of a hit when dealing with a bunch of objects, however the fact
that all data is encapsulated inside of an object is something that is very
desirable... no?

Thanks for your thoughts and discussion.
Britt Mileshosky

[mpwoodward *TMM*]

sonoflight wrote:

> Hello all, I'm curious about my current development methods with CFMX 6+ and
> your opinions. I wonder if it is possible to go too far with "objectifying"
> things in Coldfusion. Take this simple example.

It's always possible to have too much of a good thing. ;-)

> An application keeps track of current events in a database. I create a
> component / class that represents an Event with all its methods like getTime(),
> getDate(), and getDescription(). Now I create another component / class, an
> EventSchedule. Whenever I need to get a list of all Events, I would create an
> EventSchedule object and execute its method getAllClasses(). Now, the
> EventSchedule method, getAllClasses(), returns an array of Event objects.
> These objects were "filled" with their data using a query, looping through the
> query and adding all the Event data. Now the page that needs a list of all
> Events would create an EventSchedule object, call the method getAllEvents(),
> and then the page would receive an array of Event objects for use. Thus being
> able to loop through the array and calling the appropriate methods of each
> object.
>
> Is this overkill in object oriented design for ColdFusion?

Short answer, yes. From what you describe it sounds like you'd be WAY
better off using a simple query object for this sort of functionality.
Unless you actually need that array of objects for some reason that's a
ton of unnecessary overhead when a query object would suffice.

> From a performance
> / execution standpoint? Anything I should consider or be worried about with
> this methodology shown above? I know performance-wise, the server seems to be
> taking somewhat of a hit when dealing with a bunch of objects, however the fact
> that all data is encapsulated inside of an object is something that is very
> desirable... no?

Yes, definitely desirable but likely not necessary in that particular
situation. When you're dealing with *individual* objects all the
benefits of OO really kick in, but don't shy away from using a query
object when that's what the situation calls for.

Matt