That would be massive! I use AMFPHP extensively and love it as it is so
fast and easy. For me this is a very important part of the Flex ecosystem.
Would like to help where I can

On Mon, Aug 29, 2016 at 10:45 AM, Greg Dove <greg.d...@gmail.com> wrote:

> Chris, fyi the BinaryData class is now almost the same as as3 ByteArray
> except for the amf part missing: writeObject/readObject and amf0/amf3
> objectEncoding  iirc. I think the only other difference is multibyte text
> methods missing as well. So it could be a good candidate for adding the
> missing amf support to....or perhaps a subclass because I know Alex
> mentioned the need to keep lighter options available for 'pay as you go'
> approach.
>
> -Greg
> [sent from my phone]
>
> On 29/08/2016 8:19 PM, "Christofer Dutz" <christofer.d...@c-ware.de>
> wrote:
>
> I did write a J2ME serializer for AMF a while ago and I'm very familiar
> with the protocol.
>
> Eventually this would be a good thing for me to start writing some
> Cross-Compilable ActionScript ;-)
>
>
> As I see it the COMPILE:SWF part would be trivial ...
>
>
> Currently I'm sort of got my plate full with the upcomming conferences, but
> after that ...
>
>
> Chris
>
> ________________________________
> Von: carlos.rov...@gmail.com <carlos.rov...@gmail.com> im Auftrag von
> Carlos Rovira <carlos.rov...@codeoscopic.com>
> Gesendet: Montag, 29. August 2016 10:12:24
> An: dev@flex.apache.org
> Betreff: Re: [FlexJS] AMF support starting with in ECMAScript6?
>
> I commented in other threads in favor of AMF support since is a piece of
> the Flex eco system in witch many people based lots of apps out there.
> Supporting AMF in FlexJS means for many people change  only the Flex(Flash)
> layer for FlexJS without touching server side part.
>
> In the other hand I continue to see AMF as a great option to comunicate
> data with the server. So I think it will be other piece that will make
> FlexJS a better option over its competitors.
>
> I don't know how much effort it could be. See some AMF js ports out there,
> but although it seems the base algorithms are in place, no body makes a
> RemoteObject that could compete with the ease of use in Flex making realy
> usable.
>
> So for me is a positive vote and will be, without doubt, a great addition
> to FlexJS
>
> Thanks for pointing this Chris
>
> Carlos
>
>
>
>
>
> 2016-08-26 16:25 GMT+02:00 Alex Harui <aha...@adobe.com>:
>
> >
> >
> > On 8/26/16, 1:27 AM, "Christofer Dutz" <christofer.d...@c-ware.de>
> wrote:
> >
> > >Hi,
> > >
> > >
> > >I am currently working on my FlexJS Talks slides and as part of that I
> am
> > >discussing the History of ECMAScript. While digging up the changes in
> > >ECMAScript, I noticed that version 6 introduced typed arrays. It sounds
> > >to me as if this would be great to start working on AMF support in
> FlexJS.
> > >
> > >
> > >Think this could be a nice excercise for me during the autumn and winter
> > >months ;-)
> >
> > AMF for JS has been discussed in the past.  We could definitely use a
> > volunteer to work on it.  One starting point might be [1] but not sure
> > about licensing and whether it actually works.
> >
> > [1]
> > http://www.jamesward.com/2010/07/07/amf-js-a-pure-
> > javascript-amf-implementa
> > tion/
> >
> > >
> > >
> > >Do we have the ability to provide functionality based on the
> capabilities
> > >of the browser?
> > >
> >
> > I don't think we have any code that does that now.  ES6 would be a
> > different emitter and probably not switched at runtime.  I think folks
> > might serve different versions based on HTTP headers instead.
> >
> > You could also find a way to add code that does browser detection and
> load
> > polyfills.
> >
> > HTH,
> > -Alex
> >
> >
>
>
> --
>
> Carlos Rovira
> Director General
> M: +34 607 22 60 05
> http://www.codeoscopic.com
> http://www.avant2.es
>
>
> Este mensaje se dirige exclusivamente a su destinatario y puede contener
> información privilegiada o confidencial. Si ha recibido este mensaje por
> error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
> proceda a su destrucción.
>
> De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
> que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
> S.A. La finalidad de dicho tratamiento es facilitar la prestación del
> servicio o información solicitados, teniendo usted derecho de acceso,
> rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
> oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
> necesaria.
>

Reply via email to