Best Practices Question In Regards to Instancing Multiple CFCs That Need to Talk to Each Other

forums_noreply@adobe.com — Thu, 06 Nov 2014 17:36:54 GMT

Hello CF Fans,

I have a “best-practices” question in regards to how you recommend instancing CFCs that all need to talk to each other in a given project.

Let’s say for example you have a web application that has a bunch of different modules in it:

Online Calendar
Online Store
Blog
File Manager (uploading/downloading/processing files)
User Accounts

Each of these modules is nicely organized so that the functions that pertain to each module are contained within separate CFC files:

Calendar.cfc
Store.cfc
Blog.cfc
Files.cfc
Users.cfc

Each CFC contains functions appropriate for that particular module. For example, the Users.cfc contains functions pertaining to logging users on/off, updating account info etc…

Sometimes a CFC might need to reference a function in another CFC, for example, if the store (Store.cfc) needs to get information from a customer (Users.cfc). There are a couple ways that I’ve been playing with accomplishing this:

Within a CFC, instance the other CFC’s that you’re going to need:

<cfcomponent>

<cfset usersCFC = CreateObject(“component”,”users”) />
<cfset filesCFC = CreateObject(“component”,”files”) />

This approach seems to work for the most part unless some of the instanced CFC’s also instance the CFC’s that instance them. For example: If Users.cfc instances Files.cfc and Files.cfc also instances Users.cfc. I’ve run into problems with occasional dreaded NULL NULL errors with this probably because of some type of infinite recursion issue.

2. Another way I’ve tried to approach this is to instance any needed CFCs inside a CFC’s function scope (this seems to prevent the recursion issues):

<cfcomponent>

<cfset var local = structNew() />

<cfset local.usersCFC = CreateObject(“component”,”users”) />
           <cfset local.filesCFC = CreateObject(“component”,”files”) />

My concern with this approach is that it may not be as efficient because you wind up instancing the same CFC’s multiple times for each function that needs it but it does solve the problem of recursion by isolating the CFCs to their respective functions.

One thing I thought of, based on some things I’ve seen online and articles on object oriented programming, is taking advantage of a “Base.cfc” which uses the “extends” property to instance all of the CFC’s in the application. However, I’ve never tested this type of setup before and I’m not sure if this is the ideal way to allow all my CFC’s to talk to each other especially since I believe using extends overwrites functions if any of them share a common function name (e.g. “init()”).

How do you tackle this type of setup in your own applications? I’d love to hear your thoughts!

Adobe Community: Message List - Best Practices Question In Regards to Instancing Multiple CFCs That Need to Talk to Each Other

Best Practices Question In Regards to Instancing Multiple CFCs That Need to Talk to Each Other