Sean - I knew you were going to say that, however, I can not help but feel that that execution model is inherently evil, and does nothing to help code reuse.
Personally, I do not see much use for Remoting as a webservice, at least beyond fundamental operations. By building a fascade a CFC is forced to return control to the application developer, in my case, revealing far more information and control than I would like, and further increasing development time for both ColdFusion and Flash. The intent was a black box: the user requests, the CFC figures out how to handle it and returns, not vice-versa. The problem is, in my case, that an outside developer could potentially unnecessarily burdening the server with requests to rebuild a query because an overly agressive application and would ruin overall performance for everyone. Hence, it's something that I need the CFC should control. That doesn't even go to the fact that code that could be handled in one place is now pushed out to every application built around it... so much for reuse. In short, for Flash Remoting to be more than a 'toy', there needs to be a mechanism that keeps the object resident at least for the term of execution. Mike ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm
