I agree with Roland, here at our office we have migrated to Mach-ii, and one of the first things we did for all applications was to create a controller cfc that extended mach-ii and intern called the actual working cfc's to do the work (which do not extend mach-ii). The thought here is that it does not matter if we use mach-ii or not, our CFC's are still usable. It is a little extra work up front, but it is well worth it in the end. It really provides a lot more flexibilty in the application, it is also allowing multiple applications to work better together, without being coupled to one another.
Ken. -- Ken Ingle [EMAIL PROTECTED] http://www.kicweb.com/blog On Thu, 11 Nov 2004 17:57:53 -0500, Roland Collins <[EMAIL PROTECTED]> wrote: > Or you could just create Fa�ade CFCs in the parent app that expose only what > the child applications need. Then when you change the parent app, the only > thing you need to change to make sure the child apps still work is the > inner-workings of the Fa�ade, not the child apps them selves. > > Roland > > > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf > Of Bill Rawlinson > Sent: Thursday, November 11, 2004 5:47 PM > To: [EMAIL PROTECTED] > Subject: Re: [CFCDev] Separating cohesive applications > > based on what little bit you have said in this post I think > webservices are a great solution to your problem. > > You do have the extra overhead in connecting to the webservice - but > it will make the functionality infiniately more usable and will remove > any direct coupling between how each application works. > > On Thu, 11 Nov 2004 16:07:27 -0600, Joe Ferraro <[EMAIL PROTECTED]> wrote: > > > > > > > > We have some applications, all mach-ii, that have become heavily reliant > on > > each other. A "parent" application feeds content such as products, prices, > > and tracking information to the "child" applications. Problem with this is > > when there is a modification to the way that the parent system works, it > has > > a tendency to break the children applications. I'm brainstorming a way > that > > we can separate these applications with the following specifications: > > > > > > > > 1) Framework independence, I would like the child applications to > not > > have to be mach-ii even though the parent application is. Right now the > > applications call the parent application listeners directly which I would > > like to do away with. > > > > 2) Ability for child applications to not be ColdFusion. I would like > > the opportunity to allow applications that are not ColdFusion to still be > > able to retrieve information from the parent. I'm thinking webservices for > > this, but I would like public input on this. > > > > > > > > Could I make a set of webservices within the parent application and access > > it that way? Would that make sense? What are your thoughts on a good > method > > to keep the parent and children separate? > > > > > > > > Thanks a lot > > > > > > > > Joe Ferraro > > > > Web Application Developer > > > > Ken Cook Co. > > -- > Bill > http://blog.rawlinson.us > ---------------------------------------------------------- > 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 > [EMAIL PROTECTED] > > ---------------------------------------------------------- > 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 > [EMAIL PROTECTED] > ---------------------------------------------------------- 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 [EMAIL PROTECTED]
