The AMF3 performance is huge compared to SOAP/XML. If you try to send a lot of data over the wire you will notice the difference and why nobody uses web services if they can use AMF instead. Another thing is the programing model, since serialization/deserialization is managed by the gateway and Flash Player, you could have your java classes ready to use as remote objects with at zero cost. Productivity is the other real feature in AMF3.
On 12/3/06, Hans Elgelid <[EMAIL PROTECTED]> wrote:
Hans Elgelid wrote: What are the main advantages of AMF3 compared to AMF0? Found the following info from http://livedocs.macromedia.com/flex/2/langref/flash/net/ObjectEncoding.html AMF3 sends data over the network more efficiently than AMF0. AMF3 supports sending int and uint objects as integers and supports data types that are available only in ActionScript 3.0, such as ByteArray, XML, and IExternalizable. It is available only in ActionScript 3.0 and with servers that use AMF3 encoding, such as Flex 2. Many people seem happy with SOAP/XML solutions and AMF0 is already faster than those. http://www.themidnightcoders.com/articles/soap_vs_flash_remoting_benchmark.shtml So maybe AMF3 isn't the most important feature now? Can somebody give an example of an application where AMF3 is neccessary? / Hans Elgelid _______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
-- ::| Carlos Rovira ::| http://www.carlosrovira.com ::| http://www.madeinflex.com
_______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
