I'm not sure I see why it matters why the connection failed. If it failed,
you have to respond. You can certainly catch specific types of errors, but
unless you're doing something different depending on the error (and in this
case I'm not sure what that would be since you really have no idea why the
connection failed or if/when it might be back up), I'd think a general catch
would be fine.
On 9/21/07, Che Vilnonis <[EMAIL PROTECTED]> wrote:
>
> True... Bad example on my part. Let me rephrase then, what is the best way
> to catch cfhttp errors then when a connection, for whatever cannot be
> established?
>
> Perhaps <cfif NOT isdefined("cfcatch.type")> or <cfif cfcatch.type NEQ
> "COM.Allaire.ColdFusion.HTTPFailure">
>
> I just want to be sure I am not missing something obvious.
>
> Thanks, Che
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Create robust enterprise, web RIAs.
Upgrade to ColdFusion 8 and integrate with Adobe Flex
http://www.adobe.com/products/coldfusion/flex2/?sdid=RVJP
Archive:
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:289139
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
