I understand it is hard to get a full feel for the app from 1 paragraph of explanation.
Right now, I understand that you currently have all the employees Time Card information as part of the an employee object? Is that correct?
If so, moving all the time card functionality to a TimeCard component and adding an array of timecards to the employee CFC appears like a logical / reasonable approach.
How is a time card defined? By week? By Day? Perhaps it doesn't matter for the purpose of this conversation.
Each system user has one employee CFC and one CFC for all of the employee's timecards (January, February, etc).
I do not want to make any dramatic changes based on a guess of how things work.
I would like to keep functions in a CFC because I hope to build a Flash remoting interface in the future. One way to break it up would be to pull out all of the timecard functions into a single CFC stored in the server scope. Instead of referencing the "this" scope in the functions, I would reference "session.timecard." This would be a significant rewrite, and I am not sure if it will be any better because I do not understand the impact of storing a complete set of CFC methods in each CFC instance. I do know that if I make a change to the CFC file, the person has to log out then log back in to see the change, which hints at a potentially larger than expected RAM usage and object instantiation time because of the use of CFCs.
Thank you, Mike Chabot
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
