Dick, I think you need to spend a bit of time looking at new techniques that
are being used in fusebox. I have similar logic solutions in fusebox, mine
are just more readable.
I generally use the javascript for form validation, and the same fuseaction
with the same forms to validate any validation that is logic related. This
makes my display templates smaller therefore easier to read and any
validation logic beyond form validation is done in a act_ template. What
you are doing makes one monolithic template which would be hard to read by
another developer.
With your cybercash scenario, all you need is a switch to handle the error
or response from cybercash and cflocation changing the fuseaction. On a
timeout, you simply decide how many times you want to try the request and
reset the counter on each attempt then cflocation them to whatever logic you
have for cybercash being down.
e.g..,
<cflocation url="index.cfm?fuseaction=whatever">
So far all of the people that are not fans of fusebox simply do not know how
to use it and have spent no time reading the documentation or researching
its implementation. Do any of you have any real problems with fusebox?
----- Original Message -----
From: "Dick Applebaum" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, September 19, 2000 9:54 AM
Subject: RE: [CF-Talk] RE: Ben Forta, I call on thee (was: What is Fusebox )
> At 10:39 AM -0400 9/19/00, Dave Watts wrote:
> >
> >At Fig Leaf, our goals are not to build CF-centric applications, but
n-tier
> >applications. We partition application logic between the application
server
> >(CF), the database, the client, and potentially object tiers between the
> >application server and the database. Fusebox doesn't address how to
manage
> >that complexity, so it doesn't work for us from that approach.
> >
> >We provide complex client interfaces, using frames, JavaScript, Dynamic
HTML
> >and Flash. It's not uncommon for our applications to have one frame
> >dynamically generating the contents of another. Fusebox, with its header
and
> >footer files, is spectacularly unsuited to this.
> >
>
> I agree totally with the above!. I tend to use a lot of frames and
> client_side programming to reduce bandwith and improve the user
> experience. To accomplish this, you need to distribute much of the
> programming logic for navigation/validation and what I call
> application "lubricant" or "glue" to the client.
>
> Another technique I like to use is to combine the logic to:
>
> present a form
> validate a form
> Re-present a form in error ( with a popup explaining all errors
> Present the response to an Accepted form
>
> in a separate program module/template... it is a lot easier to
> delegate the entire process to a separate module, rather than
> distribute it among separate modules navigated by index.cfm
>
> There are times where you must invoke external operations (Cybercash,
> CFHTTP harvesting, etc). These operations can timeout (no response)
> or return an error.
>
> When this happens, you need to retry a given number of times, then
> try an alternate route.
>
> At each of these stages, you could get another, possibly different, error.
>
> Example from an early CyberCash/CashRegister implementation:
>
> Attempt 1: Cybercash - Authorization Times out (No response)
> Attempt 2: Cybercash - Authorization declined - already posted
> Attempt 3: CFHTTP CashRegister - Request Posted Item Info Times out
> Attempt 4: .......
>
> To try to do this with separate modules invoked through a an index.cfm
> "traffic cop" unnecessarily complicates the process.
>
> HTH
>
> Dick
>
>
>
>
>
>
>
>
> --------------------------------------------------------------------------
----
> Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
> To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
>
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
