hi all what's the current "best idea" when it comes to allowing CFC's access to sitewide UDF's (eg: string manip, custom queryToArrOfStruct, etc)
- use a "has-a" idea for the CFC (and then check if the other CFC exists)? - use a straight cfinclude within the CFC (and then worry about paths/mappings)? - add them to each CFC as private methods (and have a million versions)? - extend each CFC from a base that has the UDF's in them (and bloat some CFC's for no reason) using this as a guide <quote src="http://www.sys-con.com/coldfusion/article.cfm?id=655&count=5087&tot=4&page=2";> So what rule do I go by when making this determination? I ask myself the following questions: 1.� Do I have a CFC that the function is directly related to? 2.� Does the function access a database or another file? 3.� Do I need to call that function directly from Flash? 4.� Do I want/need to call that function as a Web service? If any of these are true, I put it in a CFC. </quote> in this case, I've got 4 NO's. I was first thinking of putting the functions into some CFC's within server scope but I'm stuck on the best trigger to load create them from new/reboot, without filling up the Application.cfm. any thoughts/suggestions? thanx barry.b --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
