Hi Guys, Currently I'm designing an application where there are a range of
jobs to view and the user can search on them in a whole bunch of different
ways like, all jobs I'm working on, all jobs, all unassigned jobs, all
completed jobs etc etc, and I have been wondering is it best in this
situation to have a different fuseaction for each of them or have one
fuseaction, say viewJob and then pass another variable which says which
search to do? What i have come up with so far is having seperate fuseactions
is easy as one generic form is built and a different query file feeds it
every time, but the other way, which initally seemed the better way, would
mean virtually an act file which has another <cfcase> in it which chooses
the sub option, sort of like a sub-fuseaction., in which the same thing
would happen anyway, query files would feed a form, it's just this would all
be in a file included in index.cfm. So after that is appears the one
fuseaction for each search seems better, but i worry index.cfm could balloon
in size if there are a lot of search criteria.
Has anyone had a situation similar to this before? Your thoughts are
appreciated, cheers.
Louis
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
