>> that there can only ever be a single instance available at any given time.
that's indeed how we're using it. it's a "mutha" of an object heavily "decorated" and stored in server or app scope. I think there may be a +'ve side effect doing it this way* - all requests (inc any transactions) would be finished before the changes came into effect - no wieredness as values change half-way thru a complex group of method calls. It's just I'm writing reams of init() code to pass values from the controller thru the service to the persist. It seems such a waste to have all that code just to pass values to the deepist layer - it's not needed for the intermediate layers. it feels like I'm coding kludgy VB again! and that's why I'm thinking if there's another way.. thanx barry.b *controller destroying the services and re-creating with new values -- ___________________________________________________________ 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]
