Re: [FlexJS] Re: Remote object for Flex JS

[Carlos Rovira]

That was the problem I have the test working! :)[image: Imágenes integradas
2]

2017-09-05 20:18 GMT+02:00 Alex Harui :

> Hi Carlos,
>
> Try switching flex-falcon to the develop branch.  I think the RemoteClass
> handling is in the develop branch and not feature/amf.
>
> -Alex
>
> On 9/5/17, 10:56 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
>  wrote:
>
> >Hi Alex,
> >
> >thanks, I know start to remember. That two scaffold projects was created
> >by
> >me in February and I left it incomplete and created based on PKumar and
> >Chris Dutz help. Is great that you get it to work! :)
> >
> >Know I'm trying to build with maven, so I put all 3 repos in brach
> >"feature/amf", update to latest commit and build the 3 repos with "maven
> >clean install". Then build "RemoteObjectAmfTest" and the java one
> >"SampleAmfWebApp".
> >
> >I then run "man spring-boot:run" on SampleAmfWebApp and that creates a
> >Jetty instance with that app deployed.
> >Then run RemoteObjectAmfTest and write something in first text input and
> >hit Button "send name to AMF"
> >
> >In my mac terminal console I get:
> >
> >2017-09-05 19:23:33.521  INFO 38753 --- [qtp651097767-13]
> >o.s.f.s.MessageBrokerHandlerAdapter
> >: Channel endpoint websocketAmf received request.
> >
> >But nothing on the browser. The same happened if I hit "Get Array OF Value
> >Objects"
> >
> >I think I didn't reach to get that console input when I left this test in
> >February, But did you get some result back to the browser? I understand by
> >you other emails that you get the String and the Array of VOs back to the
> >browser
> >
> >Thanks!
> >
> >--
> >Carlos Rovira
> >https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fabout.me%2
> >Fcarlosrovira&data=02%7C01%7C%7C4d91abc1c98f408cf18f08d4f487
> 9012%7Cfa7b1b5
> >a7b34438794aed2c178decee1%7C0%7C0%7C636402310449668789&
> sdata=WZEVMHFKNQhgC
> >MK%2FoVvKgo9c5rQ2hJ59Tx5cj8RRvKU%3D&reserved=0
>
>


-- 



Carlos Rovira

Director General

M: +34 607 22 60 05

http://www.codeoscopic.com

http://www.avant2.es


Conocenos en 1 minuto! 


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.

Re: [FlexJS] Re: Remote object for Flex JS

[Alex Harui]

Hi Carlos,

Try switching flex-falcon to the develop branch.  I think the RemoteClass
handling is in the develop branch and not feature/amf.

-Alex

On 9/5/17, 10:56 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
 wrote:

>Hi Alex,
>
>thanks, I know start to remember. That two scaffold projects was created
>by
>me in February and I left it incomplete and created based on PKumar and
>Chris Dutz help. Is great that you get it to work! :)
>
>Know I'm trying to build with maven, so I put all 3 repos in brach
>"feature/amf", update to latest commit and build the 3 repos with "maven
>clean install". Then build "RemoteObjectAmfTest" and the java one
>"SampleAmfWebApp".
>
>I then run "man spring-boot:run" on SampleAmfWebApp and that creates a
>Jetty instance with that app deployed.
>Then run RemoteObjectAmfTest and write something in first text input and
>hit Button "send name to AMF"
>
>In my mac terminal console I get:
>
>2017-09-05 19:23:33.521  INFO 38753 --- [qtp651097767-13]
>o.s.f.s.MessageBrokerHandlerAdapter
>: Channel endpoint websocketAmf received request.
>
>But nothing on the browser. The same happened if I hit "Get Array OF Value
>Objects"
>
>I think I didn't reach to get that console input when I left this test in
>February, But did you get some result back to the browser? I understand by
>you other emails that you get the String and the Array of VOs back to the
>browser
>
>Thanks!
>
>-- 
>Carlos Rovira
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2
>Fcarlosrovira&data=02%7C01%7C%7C4d91abc1c98f408cf18f08d4f4879012%7Cfa7b1b5
>a7b34438794aed2c178decee1%7C0%7C0%7C636402310449668789&sdata=WZEVMHFKNQhgC
>MK%2FoVvKgo9c5rQ2hJ59Tx5cj8RRvKU%3D&reserved=0

Re: [FlexJS] Re: Remote object for Flex JS

[Carlos Rovira]

Hi Alex,

thanks, I know start to remember. That two scaffold projects was created by
me in February and I left it incomplete and created based on PKumar and
Chris Dutz help. Is great that you get it to work! :)

Know I'm trying to build with maven, so I put all 3 repos in brach
"feature/amf", update to latest commit and build the 3 repos with "maven
clean install". Then build "RemoteObjectAmfTest" and the java one
"SampleAmfWebApp".

I then run "man spring-boot:run" on SampleAmfWebApp and that creates a
Jetty instance with that app deployed.
Then run RemoteObjectAmfTest and write something in first text input and
hit Button "send name to AMF"

In my mac terminal console I get:

2017-09-05 19:23:33.521  INFO 38753 --- [qtp651097767-13]
o.s.f.s.MessageBrokerHandlerAdapter
: Channel endpoint websocketAmf received request.

But nothing on the browser. The same happened if I hit "Get Array OF Value
Objects"

I think I didn't reach to get that console input when I left this test in
February, But did you get some result back to the browser? I understand by
you other emails that you get the String and the Array of VOs back to the
browser

Thanks!

-- 
Carlos Rovira
http://about.me/carlosrovira

Re: [FlexJS] Re: Remote object for Flex JS

[piotrz]

Hi Prashant,

Unfortunately it is not available in the nightly build yet. In order to
check it you will have to build yourself FlexJS SDK. Branch feature/amf . We
probably need someone who just check how Alex's changes are working and then
someone will merge it.

You can use Maven to build SDK [1]

[1]
https://cwiki.apache.org/confluence/display/FLEX/Building+FlexJS+with+Maven

Thanks,
Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
Sent from: http://apache-flex-development.247.n4.nabble.com/

Re: [FlexJS] Re: Remote object for Flex JS

[Alex Harui]

Hi Carlos,

Yes, if you look at the commits in that branch, there is a server example
in examples/amf/SampleAmfWebApp that has a ServerCustomObject.java.  In
examples/flexjs/RemoteObjectAmfTest there is a ClientCustomObject.java
with [RemoteClass] metadata that references the qualified name of
ServerCustomObject.  I'm not very knowledgable about this stuff so I may
not be following the typical pattern.

Build SampleAmfWebApp and run it (the Maven build creates a WAR file, I
don't think there is an Ant build for it).  It should set up a server on
localhost:8080.  Build RemoteObjectAmfTest and run it on SWF or JS.  Hit
the buttons and it should communicate with the server.  I have only tested
with bin/js-debug.  I haven't looked to see if the minified code works.

HTH,
-Alex

On 9/4/17, 4:03 PM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
 wrote:

>ok, I know see this is in "feature/amf"
>
>Thanks! :)
>
>2017-09-05 1:02 GMT+02:00 Carlos Rovira :
>
>> Hi Alex,
>>
>> could you provide more about your work here?
>>
>> For what you said I could infer that the work on AMF is on a branch or
>> feature branch? could you provide what branch is?
>> And the work right now makes a successful communication with a test java
>> backend to send and receive a String and an Array of custom objects?.
>>
>> So that objects could for example a org.apache.flexjs.Product, in FlexJS
>> and in Java?
>> The java test is deployed in some url? or we could get that sample code
>> java and flexjs?
>>
>> thanks
>>
>>
>>
>>
>>
>> 2017-09-04 19:12 GMT+02:00 Alex Harui :
>>
>>> Hi Folks,
>>>
>>> I just pushed changes that prove that I can get an array of custom
>>>objects
>>> from the backend.
>>>
>>> So, I'm going to declare my effort on AMF complete for now and go do
>>>other
>>> things.  Feel free to suggest what those other things are.  There is no
>>> AsyncToken API right now, so if folks have to have it, they should add
>>>it
>>> in.  It would be great to have someone try out the branch and merge it
>>> into develop.
>>>
>>> One possible "next thing" might be a similar encoder/decoder for JSON.
>>> Is
>>> this interesting to people?  Then we could test the performance of
>>>JSON vs
>>> AMF.  As a reminder, in SWF, AMF decoding is done in player code.  In
>>>JS,
>>> it is done in JS so there might be performance differences.  Having
>>>JSON
>>> encoder/decoder also allow comparison of how much data is sent from the
>>> server especially if there is compression over the network.
>>>
>>> Otherwise, I think my "next thing" will be to ponder release packaging
>>>in
>>> the new project.
>>>
>>> Thanks to everyone who helped get us to this point.
>>>
>>> -Alex
>>>
>>> On 9/3/17, 1:15 PM, "Jose Barragan" 
>>> wrote:
>>>
>>> >Hi Alex, Greg,
>>> >
>>> >Sounds great!!
>>> >
>>> >AMF always was my preference option for communicate the JS frontend
>>>with
>>> >the backend, as I always doing with Flex, but I haven't been cant
>>>found
>>> >any good implementation for use it.
>>> >
>>> >Sincerely, I think that a good AMF protocol implemetation (AsynToken,
>>> >RemoteObjects, etc...), as the best solution for binary comunication
>>> >(front-back) that I know, could make the difference with rest of JS
>>> >frameworks in favor of FlexJS.
>>> >
>>> >Currently, I'm working on similar concept to use on pure JS scenarios
>>> >(React, Redux, etc...), therefore I would be delighted to be able to
>>> >help/contribute to the project in this respect.
>>> >
>>> >Maybe woulds a good idea think on it, as FlexJS communications
>>>library,
>>> >to be used with or without the rest of framework in multiple and
>>> >diferents scenarios. I think this could cause a better penetration and
>>> >future adoption of FlexJS in many segments.
>>> >
>>> >Btw as Carlos says, I’ve very limited time and no guarantee too, but
>>>I'm
>>> >very interested in this new beginning in FlexJS.
>>> >
>>> >Thanks,
>>> >
>>> >
>>> >> On 3 Sep 2017, at 21:24, Piotr Zarzycki 
>>> >>wrote:
>>> >>
>>> >> Carlos,
>>> >>
>>> >> Any commit from was always a pleasure to read. :) I'm watching AMF
>>> >>progress
>>> >> also and happy that something is moving. I hope that we will get
>>>mature
>>> >> enough to get avant2 to FlexJS. I can say that with MDL there is
>>>been
>>> >> achieved quite a lot in some app which I helped and I think we have
>>>a
>>> >>lot
>>> >> potential there. :)
>>> >>
>>> >> Piotr
>>> >>
>>> >> 2017-09-03 20:20 GMT+02:00 Carlos Rovira :
>>> >>
>>> >>> Hi Alex, Greg,
>>> >>>
>>> >>> great to see some effort on bringing AMF/RemoteObject Support to
>>> >>>FlexJS.
>>> >>> Always say that this was *key* to success. Need to say that I just
>>> >>> commented with some people about this and as I expected that brings
>>> >>>lots of
>>> >>> interest, since people see this as a way to only redo the front in
>>> >>>flexes
>>> >>> without touching any java (or other backend tech) line of code.
>>> >>>
>>> >>> I even could propose in my company go with FlexJS to make a HTML
>>> >>>cl

Re: [FlexJS] Re: Remote object for Flex JS

[Carlos Rovira]

ok, I know see this is in "feature/amf"

Thanks! :)

2017-09-05 1:02 GMT+02:00 Carlos Rovira :

> Hi Alex,
>
> could you provide more about your work here?
>
> For what you said I could infer that the work on AMF is on a branch or
> feature branch? could you provide what branch is?
> And the work right now makes a successful communication with a test java
> backend to send and receive a String and an Array of custom objects?.
>
> So that objects could for example a org.apache.flexjs.Product, in FlexJS
> and in Java?
> The java test is deployed in some url? or we could get that sample code
> java and flexjs?
>
> thanks
>
>
>
>
>
> 2017-09-04 19:12 GMT+02:00 Alex Harui :
>
>> Hi Folks,
>>
>> I just pushed changes that prove that I can get an array of custom objects
>> from the backend.
>>
>> So, I'm going to declare my effort on AMF complete for now and go do other
>> things.  Feel free to suggest what those other things are.  There is no
>> AsyncToken API right now, so if folks have to have it, they should add it
>> in.  It would be great to have someone try out the branch and merge it
>> into develop.
>>
>> One possible "next thing" might be a similar encoder/decoder for JSON.  Is
>> this interesting to people?  Then we could test the performance of JSON vs
>> AMF.  As a reminder, in SWF, AMF decoding is done in player code.  In JS,
>> it is done in JS so there might be performance differences.  Having JSON
>> encoder/decoder also allow comparison of how much data is sent from the
>> server especially if there is compression over the network.
>>
>> Otherwise, I think my "next thing" will be to ponder release packaging in
>> the new project.
>>
>> Thanks to everyone who helped get us to this point.
>>
>> -Alex
>>
>> On 9/3/17, 1:15 PM, "Jose Barragan" 
>> wrote:
>>
>> >Hi Alex, Greg,
>> >
>> >Sounds great!!
>> >
>> >AMF always was my preference option for communicate the JS frontend with
>> >the backend, as I always doing with Flex, but I haven't been cant found
>> >any good implementation for use it.
>> >
>> >Sincerely, I think that a good AMF protocol implemetation (AsynToken,
>> >RemoteObjects, etc...), as the best solution for binary comunication
>> >(front-back) that I know, could make the difference with rest of JS
>> >frameworks in favor of FlexJS.
>> >
>> >Currently, I'm working on similar concept to use on pure JS scenarios
>> >(React, Redux, etc...), therefore I would be delighted to be able to
>> >help/contribute to the project in this respect.
>> >
>> >Maybe woulds a good idea think on it, as FlexJS communications library,
>> >to be used with or without the rest of framework in multiple and
>> >diferents scenarios. I think this could cause a better penetration and
>> >future adoption of FlexJS in many segments.
>> >
>> >Btw as Carlos says, I’ve very limited time and no guarantee too, but I'm
>> >very interested in this new beginning in FlexJS.
>> >
>> >Thanks,
>> >
>> >
>> >> On 3 Sep 2017, at 21:24, Piotr Zarzycki 
>> >>wrote:
>> >>
>> >> Carlos,
>> >>
>> >> Any commit from was always a pleasure to read. :) I'm watching AMF
>> >>progress
>> >> also and happy that something is moving. I hope that we will get mature
>> >> enough to get avant2 to FlexJS. I can say that with MDL there is been
>> >> achieved quite a lot in some app which I helped and I think we have a
>> >>lot
>> >> potential there. :)
>> >>
>> >> Piotr
>> >>
>> >> 2017-09-03 20:20 GMT+02:00 Carlos Rovira :
>> >>
>> >>> Hi Alex, Greg,
>> >>>
>> >>> great to see some effort on bringing AMF/RemoteObject Support to
>> >>>FlexJS.
>> >>> Always say that this was *key* to success. Need to say that I just
>> >>> commented with some people about this and as I expected that brings
>> >>>lots of
>> >>> interest, since people see this as a way to only redo the front in
>> >>>flexes
>> >>> without touching any java (or other backend tech) line of code.
>> >>>
>> >>> I even could propose in my company go with FlexJS to make a HTML
>> >>>client for
>> >>> our main product Avant2: http://avant2.es
>> >>>
>> >>> btw, there's some sample code that I could test in order to see if I
>> >>>can
>> >>> help. Very limited time, and no guarantee but I'm very interested in
>> >>>this
>> >>> coming as a first citizen feature in FlexJS
>> >>>
>> >>> Thanks!
>> >>>
>> >>> Carlos
>> >>>
>> >>>
>> >>> 2017-09-02 16:36 GMT+02:00 Alex Harui :
>> >>>
>>  Hi Greg,
>> 
>>  I didn't even realize the old thread was on users@ so thanks for
>> moving
>> >>> it
>>  here.
>> 
>>  I'm sure there are lots of improvements needed to make this work in
>> the
>>  general case so thanks for noticing and offering to help out.  I
>> wondered
>>  for a bit whether there already was a "collect the properties"
>> utility.
>>  Maybe we should create one that takes into account all of the issues
>> you
>>  raised.
>> 
>>  It was cool to see the reflection APIs work, so thanks for doing
>> them.
>>  BTW, you need the

Re: [FlexJS] Re: Remote object for Flex JS

[Carlos Rovira]

Hi Alex,

could you provide more about your work here?

For what you said I could infer that the work on AMF is on a branch or
feature branch? could you provide what branch is?
And the work right now makes a successful communication with a test java
backend to send and receive a String and an Array of custom objects?.

So that objects could for example a org.apache.flexjs.Product, in FlexJS
and in Java?
The java test is deployed in some url? or we could get that sample code
java and flexjs?

thanks





2017-09-04 19:12 GMT+02:00 Alex Harui :

> Hi Folks,
>
> I just pushed changes that prove that I can get an array of custom objects
> from the backend.
>
> So, I'm going to declare my effort on AMF complete for now and go do other
> things.  Feel free to suggest what those other things are.  There is no
> AsyncToken API right now, so if folks have to have it, they should add it
> in.  It would be great to have someone try out the branch and merge it
> into develop.
>
> One possible "next thing" might be a similar encoder/decoder for JSON.  Is
> this interesting to people?  Then we could test the performance of JSON vs
> AMF.  As a reminder, in SWF, AMF decoding is done in player code.  In JS,
> it is done in JS so there might be performance differences.  Having JSON
> encoder/decoder also allow comparison of how much data is sent from the
> server especially if there is compression over the network.
>
> Otherwise, I think my "next thing" will be to ponder release packaging in
> the new project.
>
> Thanks to everyone who helped get us to this point.
>
> -Alex
>
> On 9/3/17, 1:15 PM, "Jose Barragan"  wrote:
>
> >Hi Alex, Greg,
> >
> >Sounds great!!
> >
> >AMF always was my preference option for communicate the JS frontend with
> >the backend, as I always doing with Flex, but I haven't been cant found
> >any good implementation for use it.
> >
> >Sincerely, I think that a good AMF protocol implemetation (AsynToken,
> >RemoteObjects, etc...), as the best solution for binary comunication
> >(front-back) that I know, could make the difference with rest of JS
> >frameworks in favor of FlexJS.
> >
> >Currently, I'm working on similar concept to use on pure JS scenarios
> >(React, Redux, etc...), therefore I would be delighted to be able to
> >help/contribute to the project in this respect.
> >
> >Maybe woulds a good idea think on it, as FlexJS communications library,
> >to be used with or without the rest of framework in multiple and
> >diferents scenarios. I think this could cause a better penetration and
> >future adoption of FlexJS in many segments.
> >
> >Btw as Carlos says, I’ve very limited time and no guarantee too, but I'm
> >very interested in this new beginning in FlexJS.
> >
> >Thanks,
> >
> >
> >> On 3 Sep 2017, at 21:24, Piotr Zarzycki 
> >>wrote:
> >>
> >> Carlos,
> >>
> >> Any commit from was always a pleasure to read. :) I'm watching AMF
> >>progress
> >> also and happy that something is moving. I hope that we will get mature
> >> enough to get avant2 to FlexJS. I can say that with MDL there is been
> >> achieved quite a lot in some app which I helped and I think we have a
> >>lot
> >> potential there. :)
> >>
> >> Piotr
> >>
> >> 2017-09-03 20:20 GMT+02:00 Carlos Rovira :
> >>
> >>> Hi Alex, Greg,
> >>>
> >>> great to see some effort on bringing AMF/RemoteObject Support to
> >>>FlexJS.
> >>> Always say that this was *key* to success. Need to say that I just
> >>> commented with some people about this and as I expected that brings
> >>>lots of
> >>> interest, since people see this as a way to only redo the front in
> >>>flexes
> >>> without touching any java (or other backend tech) line of code.
> >>>
> >>> I even could propose in my company go with FlexJS to make a HTML
> >>>client for
> >>> our main product Avant2: http://avant2.es
> >>>
> >>> btw, there's some sample code that I could test in order to see if I
> >>>can
> >>> help. Very limited time, and no guarantee but I'm very interested in
> >>>this
> >>> coming as a first citizen feature in FlexJS
> >>>
> >>> Thanks!
> >>>
> >>> Carlos
> >>>
> >>>
> >>> 2017-09-02 16:36 GMT+02:00 Alex Harui :
> >>>
>  Hi Greg,
> 
>  I didn't even realize the old thread was on users@ so thanks for
> moving
> >>> it
>  here.
> 
>  I'm sure there are lots of improvements needed to make this work in
> the
>  general case so thanks for noticing and offering to help out.  I
> wondered
>  for a bit whether there already was a "collect the properties"
> utility.
>  Maybe we should create one that takes into account all of the issues
> you
>  raised.
> 
>  It was cool to see the reflection APIs work, so thanks for doing them.
>  BTW, you need the latest compiler to add the [RemoteClass] data to the
> >>> app
>  so the ClassAliasBead can register those classes.
> 
>  Thanks,
>  -Alex
> 
>  On 9/1/17, 4:44 PM, "Greg Dove"  wrote:
> 
> > Hi Alex,
> >
> >
> >>>

Re: [FlexJS] Re: Remote object for Flex JS

[Alex Harui]

Hi Folks,

I just pushed changes that prove that I can get an array of custom objects
from the backend.

So, I'm going to declare my effort on AMF complete for now and go do other
things.  Feel free to suggest what those other things are.  There is no
AsyncToken API right now, so if folks have to have it, they should add it
in.  It would be great to have someone try out the branch and merge it
into develop.

One possible "next thing" might be a similar encoder/decoder for JSON.  Is
this interesting to people?  Then we could test the performance of JSON vs
AMF.  As a reminder, in SWF, AMF decoding is done in player code.  In JS,
it is done in JS so there might be performance differences.  Having JSON
encoder/decoder also allow comparison of how much data is sent from the
server especially if there is compression over the network.

Otherwise, I think my "next thing" will be to ponder release packaging in
the new project.

Thanks to everyone who helped get us to this point.

-Alex

On 9/3/17, 1:15 PM, "Jose Barragan"  wrote:

>Hi Alex, Greg,
>
>Sounds great!!
>
>AMF always was my preference option for communicate the JS frontend with
>the backend, as I always doing with Flex, but I haven't been cant found
>any good implementation for use it.
>
>Sincerely, I think that a good AMF protocol implemetation (AsynToken,
>RemoteObjects, etc...), as the best solution for binary comunication
>(front-back) that I know, could make the difference with rest of JS
>frameworks in favor of FlexJS.
>
>Currently, I'm working on similar concept to use on pure JS scenarios
>(React, Redux, etc...), therefore I would be delighted to be able to
>help/contribute to the project in this respect.
>
>Maybe woulds a good idea think on it, as FlexJS communications library,
>to be used with or without the rest of framework in multiple and
>diferents scenarios. I think this could cause a better penetration and
>future adoption of FlexJS in many segments.
>
>Btw as Carlos says, I’ve very limited time and no guarantee too, but I'm
>very interested in this new beginning in FlexJS.
>
>Thanks,
>
>
>> On 3 Sep 2017, at 21:24, Piotr Zarzycki 
>>wrote:
>> 
>> Carlos,
>> 
>> Any commit from was always a pleasure to read. :) I'm watching AMF
>>progress
>> also and happy that something is moving. I hope that we will get mature
>> enough to get avant2 to FlexJS. I can say that with MDL there is been
>> achieved quite a lot in some app which I helped and I think we have a
>>lot
>> potential there. :)
>> 
>> Piotr
>> 
>> 2017-09-03 20:20 GMT+02:00 Carlos Rovira :
>> 
>>> Hi Alex, Greg,
>>> 
>>> great to see some effort on bringing AMF/RemoteObject Support to
>>>FlexJS.
>>> Always say that this was *key* to success. Need to say that I just
>>> commented with some people about this and as I expected that brings
>>>lots of
>>> interest, since people see this as a way to only redo the front in
>>>flexes
>>> without touching any java (or other backend tech) line of code.
>>> 
>>> I even could propose in my company go with FlexJS to make a HTML
>>>client for
>>> our main product Avant2: http://avant2.es
>>> 
>>> btw, there's some sample code that I could test in order to see if I
>>>can
>>> help. Very limited time, and no guarantee but I'm very interested in
>>>this
>>> coming as a first citizen feature in FlexJS
>>> 
>>> Thanks!
>>> 
>>> Carlos
>>> 
>>> 
>>> 2017-09-02 16:36 GMT+02:00 Alex Harui :
>>> 
 Hi Greg,
 
 I didn't even realize the old thread was on users@ so thanks for
moving
>>> it
 here.
 
 I'm sure there are lots of improvements needed to make this work in
the
 general case so thanks for noticing and offering to help out.  I
wondered
 for a bit whether there already was a "collect the properties"
utility.
 Maybe we should create one that takes into account all of the issues
you
 raised.
 
 It was cool to see the reflection APIs work, so thanks for doing them.
 BTW, you need the latest compiler to add the [RemoteClass] data to the
>>> app
 so the ClassAliasBead can register those classes.
 
 Thanks,
 -Alex
 
 On 9/1/17, 4:44 PM, "Greg Dove"  wrote:
 
> Hi Alex,
> 
> 
> Nice to see this stuff progressing within the framework itself. I
>moved
> this comment to dev because of content below, and I will try to take
>a
> look
> at this, to see if I can also test things in the coming week.
> 
> I quickly looked at some of the commits, perhaps I have missed
>something
> and you may have already addressed these somewhere in the code, but
>here
> are some quick comments just in case:
> I saw some parts where you were accessing the reflection data
>directly.
> 
> Exclude static data items from variables and accessors
> for accessors and variables they can be static as well which need to
>be
> excluded
> to keep the data compact I made the output prepend a pipe char "|" t

Re: [FlexJS] Re: Remote object for Flex JS

[Jose Barragan]

Hi Alex, Greg,

Sounds great!!

AMF always was my preference option for communicate the JS frontend with the 
backend, as I always doing with Flex, but I haven't been cant found any good 
implementation for use it.

Sincerely, I think that a good AMF protocol implemetation (AsynToken, 
RemoteObjects, etc...), as the best solution for binary comunication 
(front-back) that I know, could make the difference with rest of JS frameworks 
in favor of FlexJS.

Currently, I'm working on similar concept to use on pure JS scenarios (React, 
Redux, etc...), therefore I would be delighted to be able to help/contribute to 
the project in this respect.

Maybe woulds a good idea think on it, as FlexJS communications library, to be 
used with or without the rest of framework in multiple and diferents scenarios. 
I think this could cause a better penetration and future adoption of FlexJS in 
many segments.

Btw as Carlos says, I’ve very limited time and no guarantee too, but I'm very 
interested in this new beginning in FlexJS.

Thanks,


> On 3 Sep 2017, at 21:24, Piotr Zarzycki  wrote:
> 
> Carlos,
> 
> Any commit from was always a pleasure to read. :) I'm watching AMF progress
> also and happy that something is moving. I hope that we will get mature
> enough to get avant2 to FlexJS. I can say that with MDL there is been
> achieved quite a lot in some app which I helped and I think we have a lot
> potential there. :)
> 
> Piotr
> 
> 2017-09-03 20:20 GMT+02:00 Carlos Rovira :
> 
>> Hi Alex, Greg,
>> 
>> great to see some effort on bringing AMF/RemoteObject Support to FlexJS.
>> Always say that this was *key* to success. Need to say that I just
>> commented with some people about this and as I expected that brings lots of
>> interest, since people see this as a way to only redo the front in flexes
>> without touching any java (or other backend tech) line of code.
>> 
>> I even could propose in my company go with FlexJS to make a HTML client for
>> our main product Avant2: http://avant2.es
>> 
>> btw, there's some sample code that I could test in order to see if I can
>> help. Very limited time, and no guarantee but I'm very interested in this
>> coming as a first citizen feature in FlexJS
>> 
>> Thanks!
>> 
>> Carlos
>> 
>> 
>> 2017-09-02 16:36 GMT+02:00 Alex Harui :
>> 
>>> Hi Greg,
>>> 
>>> I didn't even realize the old thread was on users@ so thanks for moving
>> it
>>> here.
>>> 
>>> I'm sure there are lots of improvements needed to make this work in the
>>> general case so thanks for noticing and offering to help out.  I wondered
>>> for a bit whether there already was a "collect the properties" utility.
>>> Maybe we should create one that takes into account all of the issues you
>>> raised.
>>> 
>>> It was cool to see the reflection APIs work, so thanks for doing them.
>>> BTW, you need the latest compiler to add the [RemoteClass] data to the
>> app
>>> so the ClassAliasBead can register those classes.
>>> 
>>> Thanks,
>>> -Alex
>>> 
>>> On 9/1/17, 4:44 PM, "Greg Dove"  wrote:
>>> 
 Hi Alex,
 
 
 Nice to see this stuff progressing within the framework itself. I moved
 this comment to dev because of content below, and I will try to take a
 look
 at this, to see if I can also test things in the coming week.
 
 I quickly looked at some of the commits, perhaps I have missed something
 and you may have already addressed these somewhere in the code, but here
 are some quick comments just in case:
 I saw some parts where you were accessing the reflection data directly.
 
 Exclude static data items from variables and accessors
 for accessors and variables they can be static as well which need to be
 excluded
 to keep the data compact I made the output prepend a pipe char "|" to
>> the
 items data fields that represent static members - the Refection API
 classes
 (TypeDefinition) support this currently.
 
 Avoid getter-only or setter-only accessors
 For accessors data, there is an 'access' field which should filter those
 only include accessors with access: 'readwrite' for serialization
 purposes.
 This field has the same values as the xml data in flash native
>> reflection.
 
 Check Overrides
 Overrides may provide duplicated data items when collected through the
 inheritance chain.
 
 This is an area that I need to test more in the Reflection classes, and
>> it
 may affect classification of accessors for serialization purposes.
 
 Overriden accessors may perhaps represent themselves differently at
 different levels iirc - I need to check this - I can't recall if I set
>> it
 up so the access status is resolved from inheritance in the data or not.
 There may be a case where only a getter or setter is overridden is a
 subclass from a getter/setter pair in a base class and the reflection
>> data
 may indicate it is writeonly or readonly (at the subclass level) when it
>

Re: [FlexJS] Re: Remote object for Flex JS

[Piotr Zarzycki]

Carlos,

Any commit from was always a pleasure to read. :) I'm watching AMF progress
also and happy that something is moving. I hope that we will get mature
enough to get avant2 to FlexJS. I can say that with MDL there is been
achieved quite a lot in some app which I helped and I think we have a lot
potential there. :)

Piotr

2017-09-03 20:20 GMT+02:00 Carlos Rovira :

> Hi Alex, Greg,
>
> great to see some effort on bringing AMF/RemoteObject Support to FlexJS.
> Always say that this was *key* to success. Need to say that I just
> commented with some people about this and as I expected that brings lots of
> interest, since people see this as a way to only redo the front in flexes
> without touching any java (or other backend tech) line of code.
>
> I even could propose in my company go with FlexJS to make a HTML client for
> our main product Avant2: http://avant2.es
>
> btw, there's some sample code that I could test in order to see if I can
> help. Very limited time, and no guarantee but I'm very interested in this
> coming as a first citizen feature in FlexJS
>
> Thanks!
>
> Carlos
>
>
> 2017-09-02 16:36 GMT+02:00 Alex Harui :
>
> > Hi Greg,
> >
> > I didn't even realize the old thread was on users@ so thanks for moving
> it
> > here.
> >
> > I'm sure there are lots of improvements needed to make this work in the
> > general case so thanks for noticing and offering to help out.  I wondered
> > for a bit whether there already was a "collect the properties" utility.
> > Maybe we should create one that takes into account all of the issues you
> > raised.
> >
> > It was cool to see the reflection APIs work, so thanks for doing them.
> > BTW, you need the latest compiler to add the [RemoteClass] data to the
> app
> > so the ClassAliasBead can register those classes.
> >
> > Thanks,
> > -Alex
> >
> > On 9/1/17, 4:44 PM, "Greg Dove"  wrote:
> >
> > >Hi Alex,
> > >
> > >
> > >Nice to see this stuff progressing within the framework itself. I moved
> > >this comment to dev because of content below, and I will try to take a
> > >look
> > >at this, to see if I can also test things in the coming week.
> > >
> > >I quickly looked at some of the commits, perhaps I have missed something
> > >and you may have already addressed these somewhere in the code, but here
> > >are some quick comments just in case:
> > >I saw some parts where you were accessing the reflection data directly.
> > >
> > >Exclude static data items from variables and accessors
> > >for accessors and variables they can be static as well which need to be
> > >excluded
> > >to keep the data compact I made the output prepend a pipe char "|" to
> the
> > >items data fields that represent static members - the Refection API
> > >classes
> > >(TypeDefinition) support this currently.
> > >
> > >Avoid getter-only or setter-only accessors
> > >For accessors data, there is an 'access' field which should filter those
> > >only include accessors with access: 'readwrite' for serialization
> > >purposes.
> > >This field has the same values as the xml data in flash native
> reflection.
> > >
> > >Check Overrides
> > >Overrides may provide duplicated data items when collected through the
> > >inheritance chain.
> > >
> > >This is an area that I need to test more in the Reflection classes, and
> it
> > >may affect classification of accessors for serialization purposes.
> > >
> > >Overriden accessors may perhaps represent themselves differently at
> > >different levels iirc - I need to check this - I can't recall if I set
> it
> > >up so the access status is resolved from inheritance in the data or not.
> > >There may be a case where only a getter or setter is overridden is a
> > >subclass from a getter/setter pair in a base class and the reflection
> data
> > >may indicate it is writeonly or readonly (at the subclass level) when it
> > >is
> > >not because of the base class definition. There could be other unusual
> > >combinations here. (e.g. setter in base class and new getter added in
> > >subclass which together provide readWrite access in the subclass but not
> > >the base class). I am intending to write tests for these cases and
> address
> > >any issues for the reflection api.
> > >
> > >That's all I can think of for now, but as mentioned, I will try to check
> > >this out in the coming week.
> > >
> > >cheers
> > >Greg
> > >
> > >
> > >
> > >On Sat, Sep 2, 2017 at 6:38 AM, Alex Harui 
> > >wrote:
> > >
> > >> Hi Folks,
> > >>
> > >> I just pushed changes that include a back port of amf.js to
> > >>ActionScript.
> > >> In doing so, the AMF code now uses the Reflection APIs that Greg Dove
> > >> contributed.  The test still only passes a String to the server, but
> in
> > >> doing so, it has to wrap the String in an AsyncMessage subclass and I
> > >> think I have watched the AMF code correctly serialize and deserialize
> > >> those FlexJS classes to AMF and back.
> > >>
> > >> Next step is to try it with an actual ValueObject.  Can someone help
> > >>with
> > >> 

Re: [FlexJS] Re: Remote object for Flex JS

[Carlos Rovira]

Hi Alex, Greg,

great to see some effort on bringing AMF/RemoteObject Support to FlexJS.
Always say that this was *key* to success. Need to say that I just
commented with some people about this and as I expected that brings lots of
interest, since people see this as a way to only redo the front in flexes
without touching any java (or other backend tech) line of code.

I even could propose in my company go with FlexJS to make a HTML client for
our main product Avant2: http://avant2.es

btw, there's some sample code that I could test in order to see if I can
help. Very limited time, and no guarantee but I'm very interested in this
coming as a first citizen feature in FlexJS

Thanks!

Carlos


2017-09-02 16:36 GMT+02:00 Alex Harui :

> Hi Greg,
>
> I didn't even realize the old thread was on users@ so thanks for moving it
> here.
>
> I'm sure there are lots of improvements needed to make this work in the
> general case so thanks for noticing and offering to help out.  I wondered
> for a bit whether there already was a "collect the properties" utility.
> Maybe we should create one that takes into account all of the issues you
> raised.
>
> It was cool to see the reflection APIs work, so thanks for doing them.
> BTW, you need the latest compiler to add the [RemoteClass] data to the app
> so the ClassAliasBead can register those classes.
>
> Thanks,
> -Alex
>
> On 9/1/17, 4:44 PM, "Greg Dove"  wrote:
>
> >Hi Alex,
> >
> >
> >Nice to see this stuff progressing within the framework itself. I moved
> >this comment to dev because of content below, and I will try to take a
> >look
> >at this, to see if I can also test things in the coming week.
> >
> >I quickly looked at some of the commits, perhaps I have missed something
> >and you may have already addressed these somewhere in the code, but here
> >are some quick comments just in case:
> >I saw some parts where you were accessing the reflection data directly.
> >
> >Exclude static data items from variables and accessors
> >for accessors and variables they can be static as well which need to be
> >excluded
> >to keep the data compact I made the output prepend a pipe char "|" to the
> >items data fields that represent static members - the Refection API
> >classes
> >(TypeDefinition) support this currently.
> >
> >Avoid getter-only or setter-only accessors
> >For accessors data, there is an 'access' field which should filter those
> >only include accessors with access: 'readwrite' for serialization
> >purposes.
> >This field has the same values as the xml data in flash native reflection.
> >
> >Check Overrides
> >Overrides may provide duplicated data items when collected through the
> >inheritance chain.
> >
> >This is an area that I need to test more in the Reflection classes, and it
> >may affect classification of accessors for serialization purposes.
> >
> >Overriden accessors may perhaps represent themselves differently at
> >different levels iirc - I need to check this - I can't recall if I set it
> >up so the access status is resolved from inheritance in the data or not.
> >There may be a case where only a getter or setter is overridden is a
> >subclass from a getter/setter pair in a base class and the reflection data
> >may indicate it is writeonly or readonly (at the subclass level) when it
> >is
> >not because of the base class definition. There could be other unusual
> >combinations here. (e.g. setter in base class and new getter added in
> >subclass which together provide readWrite access in the subclass but not
> >the base class). I am intending to write tests for these cases and address
> >any issues for the reflection api.
> >
> >That's all I can think of for now, but as mentioned, I will try to check
> >this out in the coming week.
> >
> >cheers
> >Greg
> >
> >
> >
> >On Sat, Sep 2, 2017 at 6:38 AM, Alex Harui 
> >wrote:
> >
> >> Hi Folks,
> >>
> >> I just pushed changes that include a back port of amf.js to
> >>ActionScript.
> >> In doing so, the AMF code now uses the Reflection APIs that Greg Dove
> >> contributed.  The test still only passes a String to the server, but in
> >> doing so, it has to wrap the String in an AsyncMessage subclass and I
> >> think I have watched the AMF code correctly serialize and deserialize
> >> those FlexJS classes to AMF and back.
> >>
> >> Next step is to try it with an actual ValueObject.  Can someone help
> >>with
> >> what changes would need to be made to the service to handle a custom
> >>Java
> >> class instead of just a String?
> >>
> >> One other note:  In doing the back port, I created an AMFBinaryData that
> >> works like BinaryData, but doesn't subclass it.  That's because it
> >>appears
> >> to me that APIs like writeUTF do differently things.  Maybe we can
> >>factor
> >> out some common base class at some point.  But I think you can now use
> >> AMFBinaryData.writeObject/readObject to clone objects like we do with
> >> ByteArray.  AMFBinaryData is currently only for JS, but I think it could
> >> easily hav

Re: [FlexJS] Re: Remote object for Flex JS

[Alex Harui]

Hi Greg,

I didn't even realize the old thread was on users@ so thanks for moving it
here.

I'm sure there are lots of improvements needed to make this work in the
general case so thanks for noticing and offering to help out.  I wondered
for a bit whether there already was a "collect the properties" utility.
Maybe we should create one that takes into account all of the issues you
raised.

It was cool to see the reflection APIs work, so thanks for doing them.
BTW, you need the latest compiler to add the [RemoteClass] data to the app
so the ClassAliasBead can register those classes.

Thanks,
-Alex

On 9/1/17, 4:44 PM, "Greg Dove"  wrote:

>Hi Alex,
>
>
>Nice to see this stuff progressing within the framework itself. I moved
>this comment to dev because of content below, and I will try to take a
>look
>at this, to see if I can also test things in the coming week.
>
>I quickly looked at some of the commits, perhaps I have missed something
>and you may have already addressed these somewhere in the code, but here
>are some quick comments just in case:
>I saw some parts where you were accessing the reflection data directly.
>
>Exclude static data items from variables and accessors
>for accessors and variables they can be static as well which need to be
>excluded
>to keep the data compact I made the output prepend a pipe char "|" to the
>items data fields that represent static members - the Refection API
>classes
>(TypeDefinition) support this currently.
>
>Avoid getter-only or setter-only accessors
>For accessors data, there is an 'access' field which should filter those
>only include accessors with access: 'readwrite' for serialization
>purposes.
>This field has the same values as the xml data in flash native reflection.
>
>Check Overrides
>Overrides may provide duplicated data items when collected through the
>inheritance chain.
>
>This is an area that I need to test more in the Reflection classes, and it
>may affect classification of accessors for serialization purposes.
>
>Overriden accessors may perhaps represent themselves differently at
>different levels iirc - I need to check this - I can't recall if I set it
>up so the access status is resolved from inheritance in the data or not.
>There may be a case where only a getter or setter is overridden is a
>subclass from a getter/setter pair in a base class and the reflection data
>may indicate it is writeonly or readonly (at the subclass level) when it
>is
>not because of the base class definition. There could be other unusual
>combinations here. (e.g. setter in base class and new getter added in
>subclass which together provide readWrite access in the subclass but not
>the base class). I am intending to write tests for these cases and address
>any issues for the reflection api.
>
>That's all I can think of for now, but as mentioned, I will try to check
>this out in the coming week.
>
>cheers
>Greg
>
>
>
>On Sat, Sep 2, 2017 at 6:38 AM, Alex Harui 
>wrote:
>
>> Hi Folks,
>>
>> I just pushed changes that include a back port of amf.js to
>>ActionScript.
>> In doing so, the AMF code now uses the Reflection APIs that Greg Dove
>> contributed.  The test still only passes a String to the server, but in
>> doing so, it has to wrap the String in an AsyncMessage subclass and I
>> think I have watched the AMF code correctly serialize and deserialize
>> those FlexJS classes to AMF and back.
>>
>> Next step is to try it with an actual ValueObject.  Can someone help
>>with
>> what changes would need to be made to the service to handle a custom
>>Java
>> class instead of just a String?
>>
>> One other note:  In doing the back port, I created an AMFBinaryData that
>> works like BinaryData, but doesn't subclass it.  That's because it
>>appears
>> to me that APIs like writeUTF do differently things.  Maybe we can
>>factor
>> out some common base class at some point.  But I think you can now use
>> AMFBinaryData.writeObject/readObject to clone objects like we do with
>> ByteArray.  AMFBinaryData is currently only for JS, but I think it could
>> easily have SWF code that writes to a ByteArray added to it.
>>
>> Thanks,
>> -Alex
>>
>> On 8/23/17, 10:32 AM, "Alex Harui"  wrote:
>>
>> >Hi Prashant,
>> >
>> >The AMF work is in a separate branch so make sure you get the latest
>>code.
>> > Maybe Piotr or another volunteer will merge the branch into develop
>>so it
>> >appears in the nightly.
>> >
>> >-Alex
>> >
>> >On 8/23/17, 9:52 AM, "PKumar"  wrote:
>> >
>> >>Sure, I will download the FlexJS nightly build and check it.
>> >>
>> >>On 23-Aug-2017 10:01 PM, "Alex Harui-2 [via Apache Flex Users]" <
>> >>ml+s246n1580...@n4.nabble.com> wrote:
>> >>
>> >>> Hi Prashant,
>> >>>
>> >>> If you could add to RemoteObjectAMFTest and SampleAmfWebApp to work
>> >>>with
>> >>> an actual ValueObject, that would be great!
>> >>>
>> >>> Thanks,
>> >>> -Alex
>> >>>
>> >>> On 8/23/17, 9:21 AM, "PKumar" <[hidden email]
>> >>> > wrote:
>> >>>
>> >>

[FlexJS] Re: Remote object for Flex JS

[Greg Dove]

Hi Alex,


Nice to see this stuff progressing within the framework itself. I moved
this comment to dev because of content below, and I will try to take a look
at this, to see if I can also test things in the coming week.

I quickly looked at some of the commits, perhaps I have missed something
and you may have already addressed these somewhere in the code, but here
are some quick comments just in case:
I saw some parts where you were accessing the reflection data directly.

Exclude static data items from variables and accessors
for accessors and variables they can be static as well which need to be
excluded
to keep the data compact I made the output prepend a pipe char "|" to the
items data fields that represent static members - the Refection API classes
(TypeDefinition) support this currently.

Avoid getter-only or setter-only accessors
For accessors data, there is an 'access' field which should filter those
only include accessors with access: 'readwrite' for serialization purposes.
This field has the same values as the xml data in flash native reflection.

Check Overrides
Overrides may provide duplicated data items when collected through the
inheritance chain.

This is an area that I need to test more in the Reflection classes, and it
may affect classification of accessors for serialization purposes.

Overriden accessors may perhaps represent themselves differently at
different levels iirc - I need to check this - I can't recall if I set it
up so the access status is resolved from inheritance in the data or not.
There may be a case where only a getter or setter is overridden is a
subclass from a getter/setter pair in a base class and the reflection data
may indicate it is writeonly or readonly (at the subclass level) when it is
not because of the base class definition. There could be other unusual
combinations here. (e.g. setter in base class and new getter added in
subclass which together provide readWrite access in the subclass but not
the base class). I am intending to write tests for these cases and address
any issues for the reflection api.

That's all I can think of for now, but as mentioned, I will try to check
this out in the coming week.

cheers
Greg



On Sat, Sep 2, 2017 at 6:38 AM, Alex Harui  wrote:

> Hi Folks,
>
> I just pushed changes that include a back port of amf.js to ActionScript.
> In doing so, the AMF code now uses the Reflection APIs that Greg Dove
> contributed.  The test still only passes a String to the server, but in
> doing so, it has to wrap the String in an AsyncMessage subclass and I
> think I have watched the AMF code correctly serialize and deserialize
> those FlexJS classes to AMF and back.
>
> Next step is to try it with an actual ValueObject.  Can someone help with
> what changes would need to be made to the service to handle a custom Java
> class instead of just a String?
>
> One other note:  In doing the back port, I created an AMFBinaryData that
> works like BinaryData, but doesn't subclass it.  That's because it appears
> to me that APIs like writeUTF do differently things.  Maybe we can factor
> out some common base class at some point.  But I think you can now use
> AMFBinaryData.writeObject/readObject to clone objects like we do with
> ByteArray.  AMFBinaryData is currently only for JS, but I think it could
> easily have SWF code that writes to a ByteArray added to it.
>
> Thanks,
> -Alex
>
> On 8/23/17, 10:32 AM, "Alex Harui"  wrote:
>
> >Hi Prashant,
> >
> >The AMF work is in a separate branch so make sure you get the latest code.
> > Maybe Piotr or another volunteer will merge the branch into develop so it
> >appears in the nightly.
> >
> >-Alex
> >
> >On 8/23/17, 9:52 AM, "PKumar"  wrote:
> >
> >>Sure, I will download the FlexJS nightly build and check it.
> >>
> >>On 23-Aug-2017 10:01 PM, "Alex Harui-2 [via Apache Flex Users]" <
> >>ml+s246n1580...@n4.nabble.com> wrote:
> >>
> >>> Hi Prashant,
> >>>
> >>> If you could add to RemoteObjectAMFTest and SampleAmfWebApp to work
> >>>with
> >>> an actual ValueObject, that would be great!
> >>>
> >>> Thanks,
> >>> -Alex
> >>>
> >>> On 8/23/17, 9:21 AM, "PKumar" <[hidden email]
> >>> > wrote:
> >>>
> >>> >Really great Alex,  if you  need my help in testing  or creating demo.
> >>>Do
> >>> >please let me know.
> >>> >
> >>> >On 23-Aug-2017 9:46 PM, "Alex Harui-2 [via Apache Flex Users]" <
> >>> >[hidden email] >
> >>> wrote:
> >>> >
> >>> >> Hi Prashant,
> >>> >>
> >>> >> Yes, the RemoteObjectAMFTest only tries to send a String.  To handle
> >>> >>true
> >>> >> ValueObjects we would need to leverage the amfjs class mapping.  I
> >>> added
> >>> >> code to the compiler to generate a map for the [RemoteClass]
> >>>metadata
> >>> >>but
> >>> >> I didn't hook that up on the JS side yet.  It sounds like the
> >>>interest
> >>> >>is
> >>> >> in backporting amfjs to AS and make the API similar to regular Flex.
> >>