Thanks everyone for chipping on this. Seems like we're all landing in about the same somewhat disappointing place.
For instantiation paths, various techniques work for pointing to an app-specific cfc directory. I personally have settled on having the root application.cfm set application.app_root_path from cgi.script_name when the app starts up. Instantiation paths are based off that, so far in /_assets/class/. That means no location-specific recoding is needed on that level (unless the app is moved while it's running ?!?). I use a generic method to return instances based on that setup. However, there's no good solution for app-specific inheritance trees: - You have to code your classes' inheritance trees to a known path mapping for that app. - That's true even for multiple instances of the same app on the same server -- each of them has to have a distinct path name if you want to keep their classes separate. Because of that, you have to modify the actual classes in each instance to use the map name for that instance. All told, it's not so pretty, especially the multiple instance scenario. I hope Adobromedia sees fit to enhance CF in this area; it's got a bad damage curve, where the larger the scale of deployment, the worse the problem is. Dave Merrill ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
