hi all we're trying to build a modular system where each module has a service (logic) and persist (data access) CFC that does all the hard work. There's a singleton "kernel" that provides simple global functionality (getDSN(), utils, error handeling, etc) as well as keeping track of which modules' CFC's are loaded (some are stored in server scope)
but we've got data and logic to pull in from other modules sometimes. one module might actually need to reference the service and persist of a general (across application) module. Imagine each modules' UI consisting of a multi-tabbed forms where one of the tabs (eg address maintainance) re-appears in a few places/modules, just under a different context (which module was called). I know every situation is different but here's some options that we're thinking of 1) in addition to instanciating the module's CFC's, the calling page also creates the generals' service and persist CFC's 2) get the modules service CFC to instanciate the general one as well, with the service having a facade to the genral module (same as above but not done in the calling page) 3) get the modules' persist to "talk" to the generals' persist. sort of a "trusted" inter CFC call. 4) use the kernel to broker request across modules (a bit like a remote procedure call) 5) duplicate code that does the genral stuff into each module that needs that additional functionality. any thoughts? thanx barry.b -- ___________________________________________________________ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm ---------------------------------------------------------- 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]
