greg h
It's wonderful , I feel exciting about it . My app can talk to FMS
sucessfully, the only
thing that result in failing exactly was Action Message Format version
.You do me a
great favor ,thanks a lot.
Best regards
arokyzxc
--- In flexcoders@yahoogroups.com, "greg h" <[EMAIL PROTECTED]> wrote:
>
> arokyzxc,
>
> Following at at the end is an excerpt from an article by Renaun
regarding
> Flex & FMS. The excerpt covers how to set in Flex/AS3 the correct
> NetConnection.objectEncoding when communicating with FMS 2.
>
> Full article is here:
> http://mxdj.sys-con.com/read/295379.htm
>
> Demo and downloadable source on Renaun's sample app here:
> http://renaun.com/blog/2006/10/28/139/
>
> Please post back regarding whether this helps you or not.
>
> Best regards,
>
> g
>
> EXCERPT
>
> The Flash Player 9 introduced a newer Action Message Format version
called
> AMF3. Flex 2 creates ActionScript 3.0 SWF's, but Flash Media Server is
still
> based on ActionScript 2.0 and the earlier AMF0. By default, the Flex 2
> NetConnection class uses AMF3, therefore you must tell the
NetConnection
> what object encoding to use. There are two ways to do this:
>
> var nc:NetConnection = new NetConnection();
> nc.objectEncoding = flash.net.ObjectEncoding.AMF0;
>
> or
>
> NetConnection.defaultObjectEncoding = flash.net.ObjectEncoding.AMF0;
>
> The first method changes the object encoding for the instantiated
object
> only, whereas the second method changes the object encoding for all
> NetConnections globally. With the NetConnection set to use AMF0, the
Flex
> application will know how to communicate with the FMS application
properly.
>
