[thelist] Application Architecture

[isaac]

Frank,

I use a modified version of Fusebox that Jeff passed on. AFAIK, it has alot
of similarities with the evolt 2.0 code currently in development (short of
the overly fancy URLs ;)). Due to my relative inexperience, I've probably
managed to modify it further, but I find it very easy to work within.

It uses the Application.cfm instead of the global include file of Fusebox,
and I only use action and display files (no qry_). Anyway, I can't talk with
much expertise about much of the other stuff, but I can mention the "admin"
method I use to avoid over-duplication of code.

Basically, the admin functions are integrated with the main site but are
only available to those with session.god = yes. To login as admin, you duck
into /admin/ (password protected) and your god session is activated before
you return to the main site. If you are an admin, then you'll see [add] and
[edit] links attached to content, using something like this:

<cfif session.god>
<cfoutput>
[<a class=admin
href="#cgi.script_name#?s=content&type=edit&contentid=#attributes.contentid#
">edit this content</a>]
</cfoutput>
</cfif>

Some modules are available only to admin
(add/edit/delete/update/list/display). Other modules only have
add/edit/delete/update cases restricted to admin, while normal users can
still see the content and list it.

I find building normal and admin sides of the site concurrently to speed
things up. There may however be security issues with relying on session.god,
so I'd wait for some pros to reply to this thread.


isaac