AMF for server-to-server communication?
In last couples of days I've being thinking about this, why should we only take advantage of AMF communication between a Flex/AIR app with our back-end? Now that the specifications of AMF data format were released on Labs and a lot of AMF3 implementations are already all around ( CF, Java, .NET, PHP etc), why not take advantage of this data format for server-to-server communication?
If I have a CF server and I need to consume for example data from a PHP platform, why not doing through AMF if they use AMFPHP? Or instead of consuming a .NET webservice, why not call a WebOrb endpoint?
The cf team could eventually enhance the cfinvoke and createObject to support this.
Something like
<cfinvoke amfdestination="endpointurl" method="someRemoteMethod" returnVariable="someVar"/>
or
<cfset endpoint = createObject('amfendpoint','http://someAMFEndpoint')>
<cfset result = endpoint.someMethod( arguments ) >
Not only we would get simple data types conversion automatically but also our DTOs.or
<cfset endpoint = createObject('amfendpoint','http://someAMFEndpoint')>
<cfset result = endpoint.someMethod( arguments ) >
Toughs?
Comments
[Add Comment]
That is a popular point of discussion. It has come up in three other forums to my knowledge so far. Keep reminding them of the desire for this feature and we have a better chance of seeing it reach the real world!
# Posted By John Farrar
| 2/20/08 9:56 AM
I think it's definitely worth looking into creating ways to communicate between servers in AMF. Jared Rypka-Hauer and I kicked around trying to dive into it a few years ago, but with the spec being closed, it was hard to get too far.
# Posted By Joe Rinehart
| 2/20/08 10:07 AM
[Add Comment]
