I favor the file-by-file method. Easier to see where you
are, and what you're doing. Sure it's fine for development
either way, but it's a pain to come back 6 months later and
find the page where the client wants to change the zip code
listed on the address in that thing on that one page...
> -----Original Message-----
> From: Tom Briscoe [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, April 19, 2001 1:03 PM
> To: Fusebox
> Subject: Re: Building sites by Page ID vs. Page Files
>
>
> You're right. There would have been a fuseaction included in
> my example in a Fusebox site.
>
> My point is to investigate the advantages of building a site
> file-by-file vs. a pageID method. In the first case, you'd
> create multiple "dsp" files and a fuseaction for each page of
> content. In the latter case, you'd have a single fuseaction
> which would also be passed a pageID.
>
> However, I think it's a relevant subject to web development
> in general outside of Fusebox specifically. My apologies for
> being a bit OT. : )
>
> I'd ask the list if they've favored one method or the other and why?
>
> Briscoe
>
> >>> "stas" <[EMAIL PROTECTED]> 04/19/01 01:04PM >>>
> I am not sure I understand your point. Fusebox would deal
> with that like
> this - index.cfm?fuseaction=showpage&pageid=52 , no?
>
>
> ----- Original Message -----
> From: "Tom Briscoe" <[EMAIL PROTECTED]>
>
> Aside from development time and server overhead, what
> disadvantages would a
> pageID site building method have vs. file based?
>
> Thoughts? Opinions? Any personal experiences?
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
