That certainly makes sense.

I recall seeing something about needing to use onRequest to leverage onError
in a certain fashion, but I'll be darned if I can remember where I saw
that...

- Calvin 


On 6/3/05 10:20 AM, "Sean Corfield" <[EMAIL PROTECTED]> wrote:

> On 6/3/05, Calvin Ward <[EMAIL PROTECTED]> wrote:
>> How would you recommend working around the remoting/gateway issue? Simply by
>> not using OnRequest (which impacts the ability to use OnError), or would you
>> have a different solution?
> 
> I would use a different Application.cfc and have the web services /
> remoting CFCs in their own directory. For commonality, both this
> Application.cfc and your primary own could extend the same code CFC
> (containing the common Application.cfc methods). Your primary
> (webroot) Application.cfc would then add onRequest().
> 
> Another option is to have Application.cfc's onRequestStart() method
> check if targetPage ends in ".cfc" and, if so, do
> structDelete(variables,"onRequest"); structDelete(this,"onRequest");
> (you need both).
> 
> Note that the primary reason for using onRequest() is to set variables
> scope data that is accessible in your .cfm page - this scenario simply
> doesn't apply for web service / Flash Remoting calls!



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Find out how CFTicket can increase your company's customer support 
efficiency by 100%
http://www.houseoffusion.com/banners/view.cfm?bannerid=49

Message: http://www.houseoffusion.com/lists.cfm/link=i:4:208516
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54

Reply via email to