CFCs vs. CFFUNCTIONs

[Michael Dinowitz]

While describing a methodology I'm using for a project, Dave Watts asked a very interesting question. The methodology was to cache a number of CFCs in the application scope and store user information (that will be used by the CFCs) in the session scope. Dave's question was basically "why make them CFCs? Why not just make them all CFFUNCTIONs?"
Take for example a Users CFC which contains all of the functions for user login, logout, information, etc. A single cached CFC could do it or a host of CFFUNCTIONs that are included inside a single CFINCLUDE. A third option would be to cache each CFFUNCTION into the application scope for use.
These are all interesting approaches. What are peoples thoughts on these? Does one look better than the other? Faster? More optimal?

---

[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

---