Here was my original question...
Currently there is one main .cfm that has dozens of cfincludes
> surrounded by cfifs that do logic based on a passed in page variable. e.g.
>
> someone clicks a link:
> [url]www.foo.com/bar.cfm?page=takemehere[/url]
>
> in this case the bar.cfm is the main cfm page filled with statements that
> look
> similar to this:
>
> <CFIF page is eq takemehere>
> <CFINCLUDE takemehere.cfm>
> </CFIF>
>
> Intuitively this setup seemed rather clunky to me, as I have worked with
> it
> more and more I have gotten comfortable with it ...
Bookmarks