customers really like being able to tell their clients "go to
www.ourcompany.com/clients for more information"
fuseaction=clients just doesn't have the same appeal.
At 04:28 PM 5/29/01 -0400, you wrote:
>Yeah I've had that same concern, but I've been debating with myself
>whether it's a real problem or not. One of these days I'm going to look
>through my logs to see how many users are actually coming in through
>those "easy to remember" URLs.
>
>My guess is that most people don't remember those URLs anyway. I think
>most users just go to the homepage and drill down to the appropriate
>fuseactions by clicking links/forms/etc.
>
>Do you think it's a major issue? Or a theoretical one?
>
>Steve
>
>David Vause wrote:
> >
> > I've been working with the fusebox methodology for a couple
> > of years now, and just started delving into XFB last week.
> > I converted an old fusebox app into XFB, and I'm gaining
> > basic understanding of how it works.
> >
> > I did notice a difference between the two that I'm not
> > so crazy about. Say I have my main fusebox and a circuit
> > located in a child directory called "users." What I liked
> > about standard fusebox was the use of simple URLs. For
> > example, if I want to go straight to the default fuseaction
> > in the "users" circuit, I could type
> > http://www.someurl.com/users/ directly into my browser and
> > go to the default fuseaction for that circuit. XFB
> > apparently won't allow for this. (it usually will throw
> > a 404 error.)
> >
> > Anyway, I just wanted to share my observations and see if
> > anyone else had thoughts on how to make it work both ways.
> >
> > Dave Vause
> >
> >
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
