ColdFusion Component. Introduced in CFMX, this is an object like collection of functions that allows both for cleaner organization of code as well as easy of access through web servers and related 'outside' communications.
In Pre-CFMX, this only refered to ColdFusion Extensions written in VC++, Delphi or Java. As of CFMX, this is now a catch all term for all extensions to ColdFusion from compiled CFX tags to UDFs, CF Modules, CFCs, etc.
A Framework used for code organization created in 1998 on the CF-Talk mailing list. The original concept was to take best practices of code organization and form them into a methodology with an object like ability to plug in pieces as needed. Fusebox is organized around a single File (usually index.cfm) which contains all references to files used within a sub-portion of an application (called a Fuse). The files are not called directly but are instead references only through this interface file.
Pods are a concept that was released with the Central product by Macromedia. From an article on Breeze, it seems that the concept has grown past Central into some form of standard for Flash programming. A working definition of a pod might be:
"A pod is a SWF which contains the UI, Code and initial data for an application. This application is not meant to be independent but instead is meant to be a sub-component of a larger application.
In layout terms, a webpage that has a standard header, sidebar, body and footer could be said to contain 4 pods, 1 for each section. Alternately, it can be said that each section displayed in the body section is a pod and the surrounding layout is the containing site/application."
User Defined Function. Introduced in CF 5, this is a way of taking a set piece of coding logic and placing it into an easily reusable function. In CF 5 it was limited to the syntax in CFScript. In CFMX, the new CFFunction tag allowed access to all CF code in a UDF.
What is mm.com
mm.com is a shorthand way of saying Macromedia.com.