That sounds really cool. Is more info about reflection api? I'm happy that register** support was already done and hope we could get things like [RemoteClass] or [Transient] soon.
Thanks for doing this! :) 2016-10-27 22:20 GMT+02:00 Greg Dove <greg.d...@gmail.com>: > As Alex mentioned, I think things should be ready to support AMF (and/or > potential other serialization/deserialization approaches) via Reflection. > > I already added support for registerClassAlias, getClassByAlias, and (new) > getAliasByClass,in the reflection package - note that I did not put these > in the network project (which would have been consistent with flash.net.*) > because for js it seemed to me that they would always be used in > conjunction with Reflection API. But if others feel strongly about this, > feel free to change that. > > I have not checked whether falcon handles [RemoteClass] meta to generate > registerClassAlias calls automatically. If it does then perhaps this needs > to be considered for js to use the new reflection function for this same > support. > > Current reflection support will also allow for checking for [Transient] > metadata to exclude those readwrite accessors or variables from the set of > fields determined for serialization via reflection. > > What we do not currently have is something analogous to IExternalizable, > but perhaps that could be for later (I think I may have used this only once > in the past, perhaps others use it more). > > cheers, > Greg > > > > On Fri, Oct 28, 2016 at 7:38 AM, OK <p...@olafkrueger.net> wrote: > > > Hey Carlos, > > > > > > Carlos Rovira wrote > > > Hi Olaf, I think is more about efficiency and optimization. AMF is > > binary, > > > more compacted and faster that any other method I known out there. > > > > Yes, Flex/AMF is definately faster and I remember the discussions years > ago > > about AMF regarding performance. But even if it's faster I'm not sure if > > you > > really notice it cause often there're other bottle necks that slow down > > things. > > More over I think it depends on the use case to be really profit by the > > performance lead of AMF. > > > > Don't get me wrong, it would be great if FlexJS will support AMF but I'd > > also like to say that the current lack of AMF support is no show stopper > > that makes it impossible to use FlexJS. > > In best case people maybe could just add a facade on top of their current > > backend to be able to speak JSON over http. > > > > Anyway, you are my MDL super hero, thanks again for working on it !!! ;-) > > > > Thanks, > > Olaf > > > > > > > > > > > > -- > > View this message in context: http://apache-flex- > > development.2333347.n4.nabble.com/AMFPHP-support-for-FlexJS- > > tp56066p56087.html > > Sent from the Apache Flex Development mailing list archive at Nabble.com. > > > -- 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.
