The best way to figure out how to break apart your big application is to
imagine it as a conglomeration of smaller pieces. Yes, your admin section is
separate from the consumer side. Maybe portions of your admin side would
need separate indexes from other portions of the admin site.
There's no hard-n-fast rule. A good guideline is that if you have many
Fuseboxes (many index.cfms) each only containing one to three Fuseactions,
then you might want to squeeze more into each circuit. Not a big deal though
- it's mostly for readability's sake.
Another thing to keep in mind about how to break up your site is thinking
(rudimentarily at first) about access and security. If you want to secure
your admin section, then having it in it's separate circuit (Fusebox) would
be best. Also, if you have a member's only section, the Fuseactions that
make up that area should not be in the same index.cfm as the Fuseactions
used to create non-secure sections.
Good luck, and BUY THE BOOK!
Nat Papovich
ICQ 32676414
"If it was hard to write,"
says the Real Programmer,
"it should be hard to understand."
-----Original Message-----
From: Malcolm Barclay [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 17, 2000 7:08 PM
To: Fusebox
Subject: Re: directory structure of admin application
> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--MS_Mac_OE_3054715666_1011690_MIME_Part
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
I know exactly what you mean, I am facing the same situation with my very
first fusebox app. I am going to create a separate fuse for the admin app as
it makes more sense to me for these 'fuses to be managed and maintained by
their own index.cfm file.
You then don't have to fish through one index.cfm file that contains your
main site fuseactions and the admin site fuseactions.
m
--
Malcolm Barclay
Rocket Company Pty Ltd
Australia
e-mail: [EMAIL PROTECTED]
web: http://www.rocketcompany.com
From: Jim Priest <[EMAIL PROTECTED]>
Organization: -
Reply-To: [EMAIL PROTECTED]
Date: Tue, 17 Oct 2000 20:52:46 -0400
To: Fusebox <[EMAIL PROTECTED]>
Subject: directory structure of admin application
Trying to use Fusebox on a new site - typically we build the front end
the customer sees, and then a set of 'admin tools' the client uses to
update the site. These usually live in /admin off the root.
Now I'm trying to replicate that via Fusebox - but I'm not sure if I
should reference my /admin pages via my main 'fuse' (in the root) or
create another 'fuse' to be only used by the /admin apps? The admin
pages usually don't share any common header/footer so I don't need the
cf_bodycontent, and I need to wrap the entire /admin in some kind of
security.
Hope this makes sense - I'm looking forward to getting the book!
Thanks
Jim Priest
----------------------------------------------------------------------------
--
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
--MS_Mac_OE_3054715666_1011690_MIME_Part
Content-type: text/html; charset="US-ASCII"
Content-transfer-encoding: quoted-printable
<HTML>
<HEAD>
<TITLE>Re: directory structure of admin application</TITLE>
</HEAD>
<BODY>
I know exactly what you mean, I am facing the same situation with my very f=
irst fusebox app. I am going to create a separate fuse for the admin app as
=
it makes more sense to me for these 'fuses to be managed and maintained by
t=
heir own index.cfm file.<BR>
<BR>
You then don't have to fish through one index.cfm file that contains your m=
ain site fuseactions and the admin site fuseactions.<BR>
<BR>
m<BR>
<BR>
-- <BR>
Malcolm Barclay<BR>
Rocket Company Pty Ltd<BR>
Australia<BR>
<BR>
e-mail: [EMAIL PROTECTED]<BR>
web: http://www.rocketcompany.com<BR>
<BLOCKQUOTE><BR>
<B>From: </B>Jim Priest <[EMAIL PROTECTED]><BR>
<B>Organization: </B>-<BR>
<B>Reply-To: </B>[EMAIL PROTECTED]<BR>
<B>Date: </B>Tue, 17 Oct 2000 20:52:46 -0400<BR>
<B>To: </B>Fusebox <[EMAIL PROTECTED]><BR>
<B>Subject: </B>directory structure of admin application<BR>
<BR>
</BLOCKQUOTE><BR>
<BLOCKQUOTE><TT>Trying to use Fusebox on a new site - typically we build th=
e front end<BR>
the customer sees, and then a set of 'admin tools' the client uses to<BR>
update the site. These usually live in /admin off the root.<BR>
<BR>
Now I'm trying to replicate that via Fusebox - but I'm not sure if I<BR>
should reference my /admin pages via my main 'fuse' (in the root) or<BR>
create another 'fuse' to be only used by the /admin apps? The admin<B=
R>
pages usually don't share any common header/footer so I don't need the<BR>
cf_bodycontent, and I need to wrap the entire /admin in some kind of<BR>
security.<BR>
<BR>
Hope this makes sense - I'm looking forward to getting the book!<BR>
<BR>
Thanks<BR>
Jim Priest<BR>
<BR>
<BR>
---------------------------------------------------------------------------=
---<BR>
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=3Dlists&a=
mp;body=3Dlists/fusebox or send a message to
[EMAIL PROTECTED]=
with 'unsubscribe' in the body.<BR>
</TT></BLOCKQUOTE><TT><BR>
</TT>
</BODY>
</HTML>
--MS_Mac_OE_3054715666_1011690_MIME_Part--
----------------------------------------------------------------------------
--
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
