Title:
Bug 82820:(Watson Migration Closure)[CF10 Enhancement Request] Support for calling remoting services
| View in TrackerStatus/Resolution/Reason: Closed/Deferred/
Reporter/Name(from Bugbase): Phil Haeusler / Phil Haeusler (phil haeusler)
Created: 05/06/2010
Components: Language
Versions: 9.0
Failure Type: Unspecified
Found In Build/Fixed In Build: 0000 /
Priority/Frequency: Normal / Unknown
Locale/System: English / Platforms All
Vote Count: 1
Problem:
[CF10 Enhancement Request] Support for calling remoting services
Method:
Add support for calling Remoting Endpoints in a similar way that local CFCs can be access as a WebService. Suggested syntax
CreateObject(type="remoting", endpoint="http://localhost/flex2gateway", destination="ColdFusion")
Creating a ColdFusion application across distributed servers would gain performance benefits from being able to communicate through the Remoting AMF protocol compared with the overhead of WebService calls. This would also allow CF to leverage other remote services exposed through BlazeDS.
Additionally, add support for identifying where known types are returned from the remote service and create the correct type on the calling server i.e. If a ColdFusion component is returned through a remoting call, ColdFusion should identify and create the correct CFC on the calling server rather than a standard Java stub object. By implementing this the calling code can then operate without needing to know the remote implementation. If a CFC is returned, the calling code should receive a CFC to work with - i would expect that this would only include the properties that have been explicity defined through <cfproperty> tags in the remote component.
Result:
n/a
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3041415
External Customer Info:
External Company:
External Customer Name: Phil Haeusler
External Customer Email: 361F280E425B9CD5992015D5
External Test Config: 05/06/2010Attachments:
Comments: