@Ronan,
I have read through the MX Coding GuideLines before, about a year ago
though, I'll have to give it another read through to see if perhaps I
missed something that is relevant here, never-the-less that is always
a good resource.
Regarding 1 - As of right now, I completely agree with you.
Regarding 2 - What more common approach where you thinking of? Having
a separate DAO and Gateway? Do you personally separate what goes in
what purely by if it returns or deals with more than 1 record? Perhaps
having the Gateway return objects and talk to the DAO for all the
queries is the way to go?

@Jaime,
Exactly what Peter said about the IBO.

@Peter,
I first stumbled across the idea of an IBO on your site and thought it
was genius. At the time it was still over my head. After sinking in
for a while it all made sense. I ended up creating my own
implementation of it to help me understand it better. Also my
implementation ties in with my BaseInstanceData object, so that I can
easily convert an object from a standard bean to an IBO, just by
changing the super to be the BaseIboInstanceData instead of
BaseInstanceData. Have used the IBO in about 5 projects now and it has
worked absolutely beautifully. I know there are a few implementations
of it out there now and I've always wondered, was it originally your
idea? Btw, thanks for the great blogging!

Thanks again and keep the input coming,

Greg
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"CFCDev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cfcdev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to