At 02:25 PM 5/10/2004, you wrote:
>On May 10, 2004, at 11:08 AM, Alexander Sherwood wrote:
>>Quick questions: does "remote" invocation strictly signify a SOAP-based request or
>>can a CFC called via a form submission (component.cfc?method=test) be considered a
>>"remote" request as well?
>
>"remote" makes a method available to be called:
>1. via the web (as a FORM post/get or a URL link)
>2. via Flash Remoting
>3. via SOAP as a web service
>4. via direct invocation locally
>
>You can detect #2 I think using isDefined("flash") (looking for the "flash" scope??).
>You can detect #3 using isViaSOAP().
>
>I don't think you can tell the difference between #1 and #4.
> Why do you need to know how it's called?
Thanks Sean - the exact answer I was looking for.
The reason is this: The CFC can be invoked from a Mach-II like framework, OR remotely,
where the context of the framework doesn't exist. If an error is caught in the CFC
while invoked from within the framework, the exception is passed to an event that
formats the HTML output for the user.
In this case, I'd like to circumvent the normal exception handling routine and
redirect to one designed for remote invocation. I do so processing on the exception
before it is caught and raised to the framework, and I'd like to skip this and pass
the CFCATCH object to a second routine.
I was planning to look at the invocation method and determine which error handling
routine to use, but this might not be possible.
Any suggestions?
>Regards,
>Sean
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev'
in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported
by Mindtool, Corporation (www.mindtool.com).
An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
