0

I currently have my model and controller cfc's extend a cfc, via a Proxy component, that has all my functions. This makes all those UDF's available everywhere in the app. Are there security or performance risks in doing this? I use my models in an OO fashion. Including these functions like this makes them a part of each object as well. Specifically, could that cause performance issues when creating a lot of objects in a single page request?

I'm using CF 9 and 10 with this framework.

Thanks!

James A Mohler
  • 11,060
  • 15
  • 46
  • 72
JamesRLamar
  • 908
  • 1
  • 11
  • 22

1 Answers1

2

I think this is less a security/performance concern and more a... "ick" concern. ;) CF, especially in 9 and 10, has very fast performance, especially after the first hit. I remember doing some testing with including a 1000 or so UDFs and after the initial hit it was pretty much instantaneous. That being said, just because you can do it doesn't mean you should do it. The Application.cfc is specifically built as a way to manage your Application and how it acts. Your model/service/controller CFCs should not be extending them. The normal rule for extension is "Does A pass the 'Is A' test for B?" and your CFCs definitely are not "Is A" Application.cfc type.

What I'd recommend instead is to create a CFC for your utility functions. Heck, call it util.cfc. Then if your model or other CFCs need these functions, inject them in via a setter (and something like ColdSpring could make this even easier).

Raymond Camden
  • 10,661
  • 3
  • 34
  • 68
  • Ahh. I realized that I made an untrue statement. I used to include my functions in Application.cfc and then extend it, but for the very reasons you brought up and changed it have the model cfc extend just the functions cfc via a Proxy cfc. That being said, the tests you ran were the kind of information I was looking for. Now does that sound so bad anymore? – JamesRLamar Aug 30 '12 at 16:32