Yes Hank, it's on the todo's and infact, I'll bring it up in our meeting today.  We've been talking to the guy that originally posted the AMF3 spec and we're looking at having someone implement that with Red5.

yes, it's definitly something thats a priority with us as well ;)

JG

On 6/18/06, hank williams <[EMAIL PROTECTED]> wrote:
> And you just need one line in your flex code:
> NetConnection.defaultObjectEncoding =
> flash.net.ObjectEncoding.AMF0;
>  when red supports amf3, just delete the line.. no worries at all
>

Unfortunately, this is not correct. I have had dozens of discussions
with adobe people and people on the lists, and so I am fairly educated
on this issue.

What you are talking about is that at the low level, you can turn on
AMF0 support. But Macromedia no longer supports remoting with AMF0 and
if you just try to use remoteObject with flex and just set AMF0, it
will *not* work.

The problem is that remoting != AMF0. Remoting is *built on top of*
AMF0. Its like just because you have tcp/ip doesnt mean you have mail.
When adobe built their new remoting model for Flex, they decided not
to make it backwards compatible with AMF0. Amazingly they decided they
could make it compatible with web services, but not with their own,
existing technology. There are some people who have tried to do some
hacks, with limited success. But at a mimimum, there is *much* more
code involved than just changing/adding one line.

One example of the problem is data conversion. For example data
conversion of recordsets is something that I rely on extensively. With
the old remoting model you could send a jdbc resultSet from the
server, and it would automatically be converted into a flash
recordset. This is built into the remoting layer that sits on top of
AMF0.

So at this point it is clear that Adobe has totally abandoned and
orphaned this technology in favor of a non backwards compatible
remoting solution built on AMF3 and forcing people to pay for either
FDS or ColdFusion for something that already worked. So I am just
looking for an open source AMF3 compatible java server, since that is
the only way I can see to work with my existing codebase short of some
incomplete hack, or spending a month figuring out how to build wsdl
files.

Regards
Hank


>
> On 6/18/06, hank williams <[EMAIL PROTECTED] > wrote:
> >
> Is supporting AMF3 in the near term roadmap?
>
> I have been using openAMF and that project doesn't seem to be in
> business anymore, and my entire project is based on being able to do
> remoting in java. I remember some discussion about this but I am
> wondering if it is a far off plan or if it is imminent.
>
> Regards,
> Hank
>
> _______________________________________________
> Red5 mailing list
> [email protected]
> http://osflash.org/mailman/listinfo/red5_osflash.org
>
>
>
> --
> . m a r c o s    a u g u s t o  ;
>
> .e onde houver fé, que eu leve a dúvida.
> _______________________________________________
> Red5 mailing list
> [email protected]
> http://osflash.org/mailman/listinfo/red5_osflash.org
>
>
>

_______________________________________________
Red5 mailing list
[email protected]
http://osflash.org/mailman/listinfo/red5_osflash.org



--
John Grden - Blitz
_______________________________________________
Red5 mailing list
[email protected]
http://osflash.org/mailman/listinfo/red5_osflash.org

Reply via email to