On Thu, 13 Jan 2005 17:31:47 -0500, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I prefer in generic terms to decouple comments and articles and use > something to aggregate them, because I know that comments are a generic > enough object to be re-used (the web illustrates this). > > ... > > I think the only real argument to put on the table when designing this systems > is "will this child be re-used in other objects or better yet shared". If > that answer is yes, break the relationship away imho. > Okay, let's say that a web site has both a blog and a product catalog. While blog entries and products are generally unrelated concepts, both products and blog entries can have comments. It's possible to disable commenting on an individual product or blog entry. And a product or blog entry that has commenting enabled may not actually have any comments. In this case, I may only have one Comment.cfc that is shared by both the product catalog and blog applications. There's only one copy of Comment.cfc on the server. If that's the case, I wouldn't change anything about the way I designed the blog application. Just as a BlogEntry can hold references to Comment objects, a Product could hold references to Comment objects. Patrick -- Patrick McElhaney 704.560.9117 http://pmcelhaney.blogspot.com ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
