On Feb 1, 2008 6:57 PM, Paul Marcotte <[EMAIL PROTECTED]> wrote: > I'm thinking it's realistic to have multiple message delivery sub-systems, > E-mail, SMS, IM, perhaps others. So a NotificationService would act as a, > ahem, facade to the underlying system. Not sure if my terminology is > correct, but that's part of my longer term vision.
Yes, I think that's very viable. When I work with abstractions in my systems, I often try to pick names that are generic enough to allow that sort of layering. In other words, I probably wouldn't have an email service at first but I would have a notification service (that happens to use email for its transport). Initially it would deliver a notification object and notification.send(user) would use the underlying service to actually send the message. The service would use <cfmail> directly at first. If I needed something other than email, I'd refactor notificationService at that point and separate out an emailService, then add an smsService or whatever. That way no code that used notificationService would need to have naming refactoring applied (because it wouldn't be emailService in the first place). -- Sean A Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ "If you're not annoying somebody, you're not really alive." -- Margaret Atwood --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
