I'd like some
opinions or suggestions on how I should structure my CFCs for the requirements
listed below.
I'm currently
rebuilding our academic intranet site. This site contains information for
students, faculty and employees.
Here is where it
gets confusing (at least for me): A person may be a faculty, student,
employee or any combination of the above. Faculty and students will see a
list of the courses they teach or attend, respectively.
Examples: I'm only
an employee. My direct manager is all three. My co-worker is an
employee and student.
Each type of person
has some similarities, but many differences. Currently, I use a query
object that contains records if you are one of these types. I also only
use a single "user" CFC that is stored in the session scope.
My first question
is, should I, and how would I, develop a CFC structure that would allow for
these different types of people?
My second question
is, where is "course information" stored? Do I store it in a
"course-related" CFC or as part of the user CFC? In this system, courses
don't really exist without users. In other words, I probably won't do
anything with a course that doesn't directly tie back to at least one
user.
Any
suggestions?
M!chael A.
Dawson
Group Manager, Programming
and Software Development
Office of Technology
Services
University of
Evansville
1800 Lincoln
Avenue
Evansville, IN
47722
812-479-2581
