At that level I would only add more layers of abstraction if needed. For example, let's say you had to start using multiple notification services, and each service needed to send out email. You also want to make sure that all emails being sent out had some common elements, like styling, or a signature, or a logo, etc. Well that would make a good case for abstracting away the email piece, and re-using all that common code. But I wouldn't bother until the use-case came up.
Baz On Jan 31, 2008 8:49 PM, Robert Gatti <[EMAIL PROTECTED]> wrote: > > Something I've done in the past for emails was to utilize custom tags. > I'll make a custom tag that takes the params I need and generates the > formatted portion of the email, or wraps provided content in a layout > and style. Then the only thing I need is a > > <cfmail ...> > <cf_notificationEmail ......> > content > </cf_notificationEmail> > </cfmail> > > > I know this is not OO in the sense that is uses components but it does > compartmentalize the code into a very reusable chunk and minimizes the > overhead of writing an entire messaging api. > > > Robert > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
