One of our developers created a room reservation system for our intranet. The developer came from a Java background, and his code was (relatively) object-oriented.
The main screen shows room availability throughout the day, and instantiates 20 room or "room-day" objects, each of which contains a "reservations" objects.
It was running a little slower than we wanted it too, so as a test I wrote a simple page that produces more-or-less the same output from a query, rather than instantiating all the objects. It runs in one-tenth of the time.
I imagine the object-oriented approach is going to be more flexible and easier to maintain in the long run, but I wonder how much overhead is involved in instantiating all the CFCs. I know I haven't provided a ton of details, but has anyone here had a similar (or dissimilar) experience, or opinions on occasions when the object-oriented approach is too inefficient?



