Do something like
http://servername/circuitname/index.cfm/fuseaction/var1/value1/var2/value2
That way there's no question marks or telltale ampersands in the URL (after
all, for all the robot knows that url may actually be something like
http://server/dirname.ext/dirname/dirname(+/index.html_implied).
Michel Vuijlsteke
Netpoint NV
-----Original Message-----
From: Mike Craig [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 08, 2001 10:43 PM
To: Fusebox
Subject: RE: arguments **against** fusebox
Where is an example of this kind of searching implementation. I always
figured this to be the only major shortcoming because most index services
would find the content but not know how to build the link, since everything
is routed through index.cfm as a fuseaction. I would interested to find out
how this can best be accomplished...I will look through the book again but I
do not recall seeing anything about the issue.
-----Original Message-----
From: Roger B. [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 08, 2001 1:09 PM
To: Fusebox
Subject: RE: arguments **against** fusebox
> There is a good article that compares different cold fusion application
> frameworks (and fusebox as a methodology) in sys-con's ColdFusion
> Developer's Journal. The article list pros and cons of each
> framework/methodology.
As others have pointed out, the "good" of the article is questionable. If
nothing else, it contains one completely false statement that could have
been checked with virtually no effort... Fuseboxed sites *can* and routinely
*are* indexed by search engines.
--
Roger
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
