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 :
> As Alex mentioned, I think things should be ready
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
i
I have to disagree with Olaf here. In our company the entire backend is using
AMFPHP. Changing that to JSON and changing the frontend code as well is not a
viable option. If AMFPHP works in FlexJS there would not be any changed
required on both ends. Just making a point here that use cases indee
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
I am digging in to AMFJS and tested it with AMFPHP & Blazeds. Currently i am
trying to use AMFJS functions in FlexJS side. I am also looking the FlexSDK
RemoteObject implementation and registerclassAlias implementation, so that i
can get more information on this.
--
View this message in contex
On 10/27/16, 8:44 AM, "carlos.rov...@gmail.com on behalf of 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. in
>terms
>of usability is as well more easy to work with.
>
>I'm afr
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. in terms
of usability is as well more easy to work with.
I'm afraid that AMF could not be successful as JSON maybe due to people not
know about the openness
There's a thread in the users list which might anser some your questions [1].
>From my perception REST with JSON is become some kind of de facto standard
these days.
Even if AMF is maybe technically the better choice, in times of API driven
design it might be also important
to provide reusable AP
Hi Fréderic,
thanks for joining :)
AMF is currently not supported, but it was discussed several times in the
list.
Many of us agree that AMF is currently the best communication protocol out
there (I even don't understand the JSON success taking into account AMF is
open source specification and wa
