ok, I know see this is in "feature/amf" Thanks! :)
2017-09-05 1:02 GMT+02:00 Carlos Rovira <carlos.rov...@codeoscopic.com>: > 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 <aha...@adobe.com.invalid>: > >> 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" <jose.barra...@codeoscopic.com> >> 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 <piotrzarzyck...@gmail.com> >> >>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 <carlosrov...@apache.org>: >> >> >> >>> 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 <aha...@adobe.com.invalid>: >> >>> >> >>>> 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" <greg.d...@gmail.com> 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 <aha...@adobe.com.invalid >> > >> >>>>> 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" <aha...@adobe.com.INVALID> >> 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" <prashaku...@gmail.com> 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+s2333346n1580...@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] >> >>>>>>>>> <http:///user/SendEmail.jtp?type=node&node=15807&i=0>> 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] >> >>>>>> <http:///user/SendEmail.jtp?type=node&node=15807&i=1>> >> >>>>>>>>> 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. >> >>>>>>>>> In >> >>>>>>>>>>> that case, I will refactor the amfjs class map to use the one >> >>> in >> >>>>>> our >> >>>>>>>>>>> Reflection library. >> >>>>>>>>>>> >> >>>>>>>>>>> -Alex >> >>>>>>>>>>> >> >>>>>>>>>>> On 8/23/17, 9:08 AM, "PKumar" <[hidden email] >> >>>>>>>>>>> <http:///user/SendEmail.jtp?type=node&node=15804&i=0>> wrote: >> >>>>>>>>>>> >> >>>>>>>>>>>> Alex, >> >>>>>>>>>>>> >> >>>>>>>>>>>> It will really great, if this works same or mostly similar as >> >>>>>>>>> regular >> >>>>>>>>>>> Flex >> >>>>>>>>>>>> SDK. >> >>>>>>>>>>>> >> >>>>>>>>>>>> One more point on amfJS library , it also supports class >> >>>>>> mapping. >> >>>>>>>>> It >> >>>>>>>>>>> has >> >>>>>>>>>>>> one method *registerClasses* that can be used for Java class >> >>> to >> >>>>>>>>> flex >> >>>>>>>>>>>> mapping. >> >>>>>>>>>>>> >> >>>>>>>>>>>> On 23-Aug-2017 11:12 AM, "Alex Harui-2 [via Apache Flex >> >>> Users]" >> >>>>>> < >> >>>>>>>>>>>> [hidden email] >> >>>>>>>>> <http:///user/SendEmail.jtp?type=node&node=15804&i=1>> >> >>>>>>>>>>> wrote: >> >>>>>>>>>>>> >> >>>>>>>>>>>>> So, I played around with AMF today, adding SWF code for >> >>>>>>>>> RemoteObject. >> >>>>>>>>>>>>> For >> >>>>>>>>>>>>> me, the RemoteObjectAMFTest in examples/flexjs is working >> >>>>>> against >> >>>>>>>>> the >> >>>>>>>>>>>>> SampleAmfWebApp in examples/amf for both SWF and JS. I >> >>> don't >> >>>>>>>>> think >> >>>>>>>>> I >> >>>>>>>>>>>>> had >> >>>>>>>>>>>>> to touch the JS code in amf.js. That's better than I was >> >>>>>>>>> expecting. >> >>>>>>>>>>>>> Am I >> >>>>>>>>>>>>> not doing something right or is there some other problem >> >>> that >> >>>>>>>>> needs >> >>>>>>>>>>>>> solving? >> >>>>>>>>>>>>> >> >>>>>>>>>>>>> Some observations along the way: >> >>>>>>>>>>>>> >> >>>>>>>>>>>>> I was able to talk to the server in SWF code just by using >> >>>>>>>>>>>>> NetConnection.call and passing in CommandMessages and >> >>>>>>>>>>> RemotingMessages, >> >>>>>>>>>>>>> but the amf.js code seems to be sending an ActionMessage >> >>>>>> wrapped >> >>>>>>>>>>> around >> >>>>>>>>>>>>> the CommandMessage and RemotingMessage. Is that wrapping >> >>> what >> >>>>>>>>>>>>> NetConnection does? >> >>>>>>>>>>>>> >> >>>>>>>>>>>>> I'm tempted to try to refactor amf.js into several AS >> >>> classes. >> >>>>>>>>> Is >> >>>>>>>>>>> that >> >>>>>>>>>>>>> worth doing or are there bigger fish to fry? >> >>>>>>>>>>>>> >> >>>>>>>>>>>>> The amf.js code includes a Promise implementation. If we >> >>>>>>>>> refactor >> >>>>>>>>> to >> >>>>>>>>>>>>> AS, >> >>>>>>>>>>>>> should we try to use promises or make the API more >> >>> compatible >> >>>>>>>>> with >> >>>>>>>>>>>>> regular >> >>>>>>>>>>>>> Flex? I'm leaning towards compatibility with regular Flex. >> >>>>>>>>>>>>> >> >>>>>>>>>>>>> Thoughts? >> >>>>>>>>>>>>> -Alex >> >>>>>>>>>>>>> >> >>>>>>>>>>>>> On 8/21/17, 11:02 AM, "Harbs" <[hidden email] >> >>>>>>>>>>>>> <http:///user/SendEmail.jtp?type=node&node=15798&i=0>> >> >>> wrote: >> >>>>>>>>>>>>> >> >>>>>>>>>>>>>> There’s probably an advantage to converting it to FlexJS. >> >>> You >> >>>>>>>>> could >> >>>>>>>>>>>>>> probably leverage BinaryData for some of the functionality. >> >>>>>>>>>>>>>> >> >>>>>>>>>>>>>> You can also create typedefs if you want. >> >>>>>>>>>>>>>> >> >>>>>>>>>>>>>>> On Aug 21, 2017, at 8:53 PM, PKumar <[hidden email] >> >>>>>>>>>>>>> <http:///user/SendEmail.jtp?type=node&node=15798&i=1>> >> >>> wrote: >> >>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>> Alex, >> >>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>> As per my analysis & testing, AMFJS supports following >> >>>>>>>>> features: >> >>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>> - All dataType serialization & deserialization support >> >>>>>>>>> including >> >>>>>>>>>>>>>>> Object , >> >>>>>>>>>>>>>>> Vector >> >>>>>>>>>>>>>>> - Connection with BlazeDS >> >>>>>>>>>>>>>>> - Conection with AMFPHP >> >>>>>>>>>>>>>>> - Class Mapping Support using Alias Name & Class >> >>>>>>>>>>>>>>> - Inbuilt support for sending AMF request & response >> >>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>> I also checked James ward implementation but that does >> >>> not >> >>>>>>>>>>> support >> >>>>>>>>>>>>>>> vector >> >>>>>>>>>>>>>>> and blazeds connectivity. >> >>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>> I prepared a demo for class mapping and blazeDs >> >>>>>> connection. >> >>>>>>>>> If >> >>>>>>>>>>> you >> >>>>>>>>>>>>>>> want to >> >>>>>>>>>>>>>>> check, please let me know. I will share on github. >> >>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>> one query i want to ask , can we convert this amfJS >> >>>>>> library >> >>>>>>>>> to >> >>>>>>>>>>>>> FlexJS >> >>>>>>>>>>>>>>> Typedef just like createJS library? >> >>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>> Regards, >> >>>>>>>>>>>>>>> Prashant >> >>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>> ----- >> >>>>>>>>>>>>>>> Regards, >> >>>>>>>>>>>>>>> Prashant >> >>>>>>>>>>>>>>> -- >> >>>>>>>>>>>>>>> View this message in context: >> >>>>>>>>>>>>>>> https://na01.safelinks.protection.outlook.com/?url= >> >>>>>>>>>>>>> http%3A%2F%2Fapache-fl >> >>>>>>>>>>>>> >> >>>>>>>>>>> >> >>>>>>>>> >> >>>>>>>>>>>>>>> ex-users.2333346.n4.nabble.com%2FRemote-object- >> >>>>>> for-Flex-JS-tp15510 >> >>>>>>>>>>>>>>> p >> >>>>>>>>>>>>>>> 15 >> >>>>>>>>> >> >>>>>>>>>>>>>>> 78 >> >>>>>>>>>>> >> >>>>>>>>>>>>>>> 2. >> >>>>>>>>>>>>> >> >>>>>>>>>>>>> >> >>>>>>>>>>> >> >>>>>>>>> >> >>>>>>>>>>>>>>> html&data=02%7C01%7C%7C1af098eb84194e4a169c08d4e8be >> >>>>>> bf0f%7Cfa7b1b5a >> >>>>>>>>>>>>>>> 7 >> >>>>>>>>>>>>>>> b3 >> >>>>>>>>> >> >>>>>>>>>>>>>>> 44 >> >>>>>>>>>>> >> >>>>>>>>>>>>>>> 38 >> >>>>>>>>>>>>> >> >>>>>>>>>>>>> >> >>>>>>>>>>> >> >>>>>>>>> >> >>>>>>>>>>>>>>> 794aed2c178decee1%7C0%7C0%7C636389353321386860& >> >>>>>> sdata=9Vgilc%2FEEN6 >> >>>>>>>>>>>>>>> e >> >>>>>>>>>>>>>>> QE >> >>>>>>>>> >> >>>>>>>>>>>>>>> Gj >> >>>>>>>>>>> >> >>>>>>>>>>>>>>> Dw >> >>>>>>>>>>>>> >> >>>>>>>>>>>>>>> mmQV8N952XqBSbgweg1VQ41g4%3D&reserved=0 >> >>>>>>>>>>>>>>> Sent from the Apache Flex Users mailing list archive at >> >>>>>>>>>>> Nabble.com. >> >>>>>>>>>>>>>> >> >>>>>>>>>>>>> >> >>>>>>>>>>>>> >> >>>>>>>>>>>>> >> >>>>>>>>>>>>> ------------------------------ >> >>>>>>>>>>>>> If you reply to this email, your message will be added to >> >>> the >> >>>>>>>>>>> discussion >> >>>>>>>>>>>>> below: >> >>>>>>>>>>>>> >> >>>>>>>>>>>>> https://na01.safelinks.protection.outlook.com/?url= >> >>>>>>>>>>> http%3A%2F%2Fapache-fl >> >>>>>>>>>>> >> >>>>>>>>> >> >>>>>>>>>>>>> ex-users.2333346.n4.nabble.com%2FRemote-object- >> >>>>>> for-Flex-JS-&data=02% >> >>>>>>>>>>>>> 7 >> >>>>>>>>>>>>> C0 >> >>>>>>>>> >> >>>>>>>>>>>>> 1% >> >>>>>>>>>>> >> >>>>>>>>>>> >> >>>>>>>>> >> >>>>>>>>>>>>> 7C%7C3a1ce1deff3f47dff8ef08d4ea413522% >> >>>>>> 7Cfa7b1b5a7b34438794aed2c178de >> >>>>>>>>>>>>> c >> >>>>>>>>>>>>> ee >> >>>>>>>>> >> >>>>>>>>>>>>> 1% >> >>>>>>>>>>> >> >>>>>>>>>>> >> >>>>>>>>> >> >>>>>>>>>>>>> 7C0%7C0%7C636391013164618149&s >> data=%2FOcSNyohTV1%2FJaKe%2BgW% >> >>>>>> 2BHspE% >> >>>>>>>>>>>>> 2 >> >>>>>>>>>>>>> FV >> >>>>>>>>> >> >>>>>>>>>>>>> %2 >> >>>>>>>>>>> >> >>>>>>>>>>>>> FtaoyEdCq2YOzUmq4%3D&reserved=0 >> >>>>>>>>>>>>> tp15510p15798.html >> >>>>>>>>>>>>> To start a new topic under Apache Flex Users, email >> >>>>>>>>>>>>> [hidden email] >> >>>>>>>>> <http:///user/SendEmail.jtp?type=node&node=15804&i=2> >> >>>>>>>>> >> >>>>>>>>>>>>> To unsubscribe from Apache Flex Users, click here >> >>>>>>>>>>>>> >> >>>>>>>>>>>>> <https://na01.safelinks.protection.outlook.com/?url= >> >>>>>>>>>>> http%3A%2F%2Fapache-f >> >>>>>>>>>>> >> >>>>>>>>> >> >>>>>>>>>>>>> lex-users.2333346.n4.nabble.com%2Ftemplate% >> >>>>>> 2FNamlServlet.jtp%3Fmacro >> >>>>>>>>>>>>> % >> >>>>>>>>>>>>> 3D >> >>>>>>>>> >> >>>>>>>>>>>>> un >> >>>>>>>>>>> >> >>>>>>>>>>> >> >>>>>>>>> >> >>>>>> >> >>>>>>>>>>>>> subscribe_by_code%26node%3D1%26code% >> >>>> 3DcHJhc2hha3VtYXJAZ21haWwuY29t >> >>>>>> fD >> >>>>>>>>>>>>> F >> >>>>>>>>>>>>> 8L >> >>>>>>>>> >> >>>>>>>>>>>>> TU >> >>>>>>>>>>> >> >>>>>>>>>>> >> >>>>>>>>> >> >>>>>>>>>>>>> 0MTcyMzE2NA&data=02%7C01%7C%7C3a1ce1deff3f47dff8ef08d4ea41 >> >>>>>> 3522%7Cfa7 >> >>>>>>>>>>>>> b >> >>>>>>>>>>>>> 1b >> >>>>>>>>> >> >>>>>>>>>>>>> 5a >> >>>>>>>>>>> >> >>>>>>>>>>> >> >>>>>>>>> >> >>>>>>>>>>>>> 7b34438794aed2c178decee1%7C0%7C0%7C636391013164618149& >> >>>>>> sdata=oG9TQOL2 >> >>>>>>>>>>>>> W >> >>>>>>>>>>>>> HD >> >>>>>>>>> >> >>>>>>>>>>>>> Im >> >>>>>>>>>>> >> >>>>>>>>>>>>> 7ixmXea4gFCoUw4j8b0HUsYOw7f4Pk%3D&reserved=0==> >> >>>>>>>>>>>>> . >> >>>>>>>>>>>>> NAML >> >>>>>>>>>>>>> >> >>>>>>>>>>>>> <https://na01.safelinks.protection.outlook.com/?url= >> >>>>>>>>>>> http%3A%2F%2Fapache-f >> >>>>>>>>>>> >> >>>>>>>>> >> >>>>>>>>>>>>> lex-users.2333346.n4.nabble.com%2Ftemplate% >> >>>>>> 2FNamlServlet.jtp%3Fmacro >> >>>>>>>>>>>>> % >> >>>>>>>>>>>>> 3D >> >>>>>>>>> >> >>>>>>>>>>>>> ma >> >>>>>>>>>>> >> >>>>>>>>>>> >> >>>>>>>>> >> >>>>>>>>>>>>> cro_viewer%26id%3Dinstant_html%2521nabble% >> >>>>>> 253Aemail.naml%26base%3Dna >> >>>>>>>>>>>>> b >> >>>>>>>>>>>>> bl >> >>>>>>>>> >> >>>>>>>>>>>>> e. >> >>>>>>>>>>> >> >>>>>>>>>>> >> >>>>>>>>> >> >>>>>>>>>>>>> naml.namespaces.BasicNamespace-nabble.view. >> >>>>>> web.template.NabbleNamesp >> >>>>>>>>>>>>> a >> >>>>>>>>>>>>> ce >> >>>>>>>>> >> >>>>>>>>>>>>> -n >> >>>>>>>>>>> >> >>>>>>>>>>> >> >>>>>>>>> >> >>>>>>>>>>>>> abble.view.web.template.NodeNamespace% >> >>>>>> 26breadcrumbs%3Dnotify_subscri >> >>>>>>>>>>>>> b >> >>>>>>>>>>>>> er >> >>>>>>>>> >> >>>>>>>>>>>>> s% >> >>>>>>>>>>> >> >>>>>>>>>>> >> >>>>>>>>> >> >>>>>>>>>>>>> 2521nabble%253Aemail.naml-instant_emails% >> >>>>>> 2521nabble%253Aemail.naml-s >> >>>>>>>>>>>>> e >> >>>>>>>>>>>>> nd >> >>>>>>>>> >> >>>>>>>>>>>>> _i >> >>>>>>>>>>> >> >>>>>>>>>>> >> >>>>>>>>> >> >>>>>>>>>>>>> nstant_email%2521nabble%253Aemail.naml& >> >>>>>> data=02%7C01%7C%7C3a1ce1deff3 >> >>>>>>>>>>>>> f >> >>>>>>>>>>>>> 47 >> >>>>>>>>> >> >>>>>>>>>>>>> df >> >>>>>>>>>>> >> >>>>>>>>>>> >> >>>>>>>>> >> >>>>>>>>>>>>> f8ef08d4ea413522%7Cfa7b1b5a7b34438794aed2c178de >> >>>>>> cee1%7C0%7C0%7C636391 >> >>>>>>>>>>>>> 0 >> >>>>>>>>>>>>> 13 >> >>>>>>>>> >> >>>>>>>>>>>>> 16 >> >>>>>>>>>>> >> >>>>>>>>>>> >> >>>>>>>>> >> >>>>>>>>>>>>> 4618149&sdata=IBL7nGCu8Fr2VJyGGJvN4eo2j3ciNK >> >>>>>> aqdMySmNqzEH8%3D&reserve >> >>>>>>>>>>>>> d >> >>>>>>>>>>>>> =0 >> >>>>>>>>> >> >>>>>>>>>>>>>> >> >>>>>>>>>>> >> >>>>>>>>>>>>> >> >>>>>>>>>>>> >> >>>>>>>>>>>> >> >>>>>>>>>>>> >> >>>>>>>>>>>> >> >>>>>>>>>>>> ----- >> >>>>>>>>>>>> Regards, >> >>>>>>>>>>>> Prashant >> >>>>>>>>>>>> -- >> >>>>>>>>>>>> View this message in context: >> >>>>>>>>>>>> https://na01.safelinks.protection.outlook.com/?url= >> >>>>>>>>>>> http%3A%2F%2Fapache-fle >> >>>>>>>>>>>> x-users.2333346.n4.nabble.com%2FRemote-object-for-Flex-JS- >> >>>>>>>>>>> tp15510p15803.ht >> >>>>>>>>>>> >> >>>>>>>>> >> >>>>>>>>>>>> ml&data=02%7C01%7C%7C3a1ce1deff3f47dff8ef08d4ea41 >> >>>>>> 3522%7Cfa7b1b5a7b344 >> >>>>>>>>>>>> 3 >> >>>>>>>>>>>> 87 >> >>>>>>>>> >> >>>>>>>>>>>> 94 >> >>>>>>>>>>> >> >>>>>>>>>>> >> >>>>>>>>> >> >>>>>>>>>>>> aed2c178decee1%7C0%7C0%7C636391013164618149&sdata= >> >>>>>> J3LsrJ3Zxc%2FxglCYj >> >>>>>>>>>>>> 8 >> >>>>>>>>>>>> zw >> >>>>>>>>> >> >>>>>>>>>>>> cX >> >>>>>>>>>>> >> >>>>>>>>>>>> vDzIX9nCPn0S%2Brd%2BVE9O0%3D&reserved=0 >> >>>>>>>>>>>> Sent from the Apache Flex Users mailing list archive at >> >>>>>> Nabble.com. >> >>>>>>>>>>> >> >>>>>>>>>>> >> >>>>>>>>>>> >> >>>>>>>>>>> ------------------------------ >> >>>>>>>>>>> If you reply to this email, your message will be added to the >> >>>>>>>>> discussion >> >>>>>>>>>>> below: >> >>>>>>>>>>> >> >>>>>>>>>>> https://na01.safelinks.protection.outlook.com/?url= >> >>>>>>>>> http%3A%2F%2Fapache-fl >> >>>>>>>>> >> >>>>>>>>>>> ex-users.2333346.n4.nabble.com%2FRemote-object- >> >>>>>> for-Flex-JS-&data=02%7C >> >>>>>>>>>>> 0 >> >>>>>>>>>>> 1% >> >>>>>>>>> >> >>>>>>>>> >> >>>>>> >> >>>>>>>>>>> 7C%7Cf10440168a264ce4a83308d4ea42fce0% >> >>>> 7Cfa7b1b5a7b34438794aed2c178de >> >>>>>> ce >> >>>>>>>>>>> e >> >>>>>>>>>>> 1% >> >>>>>>>>> >> >>>>>>>>> >> >>>>>>>>>>> 7C0%7C0%7C636391020812650097&sdata= >> >>> 4dXIVzqiXbxllGLy9oymfR5lLMIhps >> >>>>>> 6NQmj >> >>>>>>>>>>> p >> >>>>>>>>>>> 8t >> >>>>>>>>> >> >>>>>>>>>>> VmRVo%3D&reserved=0 >> >>>>>>>>>>> tp15510p15804.html >> >>>>>>>>>>> To start a new topic under Apache Flex Users, email >> >>>>>>>>>>> [hidden email] <http:///user/SendEmail.jtp? >> >>>>>> type=node&node=15807&i=2> >> >>>>>>>>>>> To unsubscribe from Apache Flex Users, click here >> >>>>>>>>>>> >> >>>>>>>>>>> <https://na01.safelinks.protection.outlook.com/?url= >> >>>>>>>>> http%3A%2F%2Fapache-f >> >>>>>>>>> >> >>>>>>>>>>> lex-users.2333346.n4.nabble.com%2Ftemplate% >> >>>>>> 2FNamlServlet.jtp%3Fmacro%3 >> >>>>>>>>>>> D >> >>>>>>>>>>> un >> >>>>>>>>> >> >>>>>>>>> >> >>>>>>>>>>> subscribe_by_code%26node%3D1%26code% >> >>> 3DcHJhc2hha3VtYXJAZ21haWwuY29t >> >>>>>> fDF8 >> >>>>>>>>>>> L >> >>>>>>>>>>> TU >> >>>>>>>>> >> >>>>>>>>> >> >>>>>>>>>>> 0MTcyMzE2NA&data=02%7C01%7C%7Cf10440168a264ce4a83308d4ea42 >> >>>>>> fce0%7Cfa7b1 >> >>>>>>>>>>> b >> >>>>>>>>>>> 5a >> >>>>>>>>> >> >>>>>>>>> >> >>>>>>>>>>> 7b34438794aed2c178decee1%7C0%7C0%7C636391020812650097& >> >>>>>> sdata=4dcQPrPyC3 >> >>>>>>>>>>> p >> >>>>>>>>>>> pE >> >>>>>>>>> >> >>>>>>>>>>> x36S3f%2B950UpNNwOJEfiG5e%2BGXpALg%3D&reserved=0==> >> >>>>>>>>>>> . >> >>>>>>>>>>> NAML >> >>>>>>>>>>> >> >>>>>>>>>>> <https://na01.safelinks.protection.outlook.com/?url= >> >>>>>>>>> http%3A%2F%2Fapache-f >> >>>>>>>>> >> >>>>>>>>>>> lex-users.2333346.n4.nabble.com%2Ftemplate% >> >>>>>> 2FNamlServlet.jtp%3Fmacro%3 >> >>>>>>>>>>> D >> >>>>>>>>>>> ma >> >>>>>>>>> >> >>>>>>>>> >> >>>>>>>>>>> cro_viewer%26id%3Dinstant_html%2521nabble% >> >>>>>> 253Aemail.naml%26base%3Dnabb >> >>>>>>>>>>> l >> >>>>>>>>>>> e. >> >>>>>>>>> >> >>>>>>>>> >> >>>>>>>>>>> naml.namespaces.BasicNamespace-nabble.view. >> >>>>>> web.template.NabbleNamespac >> >>>>>>>>>>> e >> >>>>>>>>>>> -n >> >>>>>>>>> >> >>>>>>>>> >> >>>>>>>>>>> abble.view.web.template.NodeNamespace%26breadcrumbs% >> >>>>>> 3Dnotify_subscribe >> >>>>>>>>>>> r >> >>>>>>>>>>> s% >> >>>>>>>>> >> >>>>>>>>> >> >>>>>>>>>>> 2521nabble%253Aemail.naml-instant_emails% >> >>>>>> 2521nabble%253Aemail.naml-sen >> >>>>>>>>>>> d >> >>>>>>>>>>> _i >> >>>>>>>>> >> >>>>>>>>> >> >>>>>>>>>>> nstant_email%2521nabble%253Aemail.naml&data=02%7C01% >> >>>>>> 7C%7Cf10440168a264 >> >>>>>>>>>>> c >> >>>>>>>>>>> e4 >> >>>>>>>>> >> >>>>>>>>> >> >>>>>>>>>>> a83308d4ea42fce0%7Cfa7b1b5a7b34438794aed2c178de >> >>>>>> cee1%7C0%7C0%7C63639102 >> >>>>>>>>>>> 0 >> >>>>>>>>>>> 81 >> >>>>>>>>> >> >>>>>>>>> >> >>>>>>>>>>> 2650097&sdata=XnllokaW1joWP0zh%2Fy1zvmzruvn% >> >>>>>> 2BneggkXh6xHdsunE%3D&reser >> >>>>>>>>>>> v >> >>>>>>>>>>> ed >> >>>>>>>>> >> >>>>>>>>>>> =0> >> >>>>>>>>>>> >> >>>>>>>>>> >> >>>>>>>>>> >> >>>>>>>>>> >> >>>>>>>>>> >> >>>>>>>>>> ----- >> >>>>>>>>>> Regards, >> >>>>>>>>>> Prashant >> >>>>>>>>>> -- >> >>>>>>>>>> View this message in context: >> >>>>>>>>>> https://na01.safelinks.protection.outlook.com/?url= >> >>>>>>>>> http%3A%2F%2Fapache-fle >> >>>>>>>>>> x-users.2333346.n4.nabble.com%2FRemote-object-for-Flex-JS- >> >>>>>>>>> tp15510p15805.ht >> >>>>>>>>> >> >>>>>>>>>> ml&data=02%7C01%7C%7Cf10440168a264ce4a83308d4ea42 >> >>>>>> fce0%7Cfa7b1b5a7b34438 >> >>>>>>>>>> 7 >> >>>>>>>>>> 94 >> >>>>>>>>> >> >>>>>>>>> >> >>>>>>>>>> aed2c178decee1%7C0%7C0%7C636391020812650097&sdata= >> >>>>>> HBbOQ1Hn1n0lAG%2FGYHd >> >>>>>>>>>> z >> >>>>>>>>>> bg >> >>>>>>>>> >> >>>>>>>>>> vrwKxd8pWLrxm46FJSAnY%3D&reserved=0 >> >>>>>>>>>> Sent from the Apache Flex Users mailing list archive at >> >>> Nabble.com. >> >>>>>>>>> >> >>>>>>>>> >> >>>>>>>>> >> >>>>>>>>> ------------------------------ >> >>>>>>>>> If you reply to this email, your message will be added to the >> >>>>>>>>> discussion >> >>>>>>>>> below: >> >>>>>>>>> >> >>>>>>>>> https://na01.safelinks.protection.outlook.com/?url= >> >>>>>> http%3A%2F%2Fapache-f >> >>>>>>>>> l >> >>>>>>>>> ex-users.2333346.n4.nabble.com%2FRemote-object-for-Flex- >> >>>>>> JS-&data=02%7C01 >> >>>>>>>>> % >> >>>>>>>>> 7C%7C5d32ae4db4c14fd8227a08d4ea476740% >> >>> 7Cfa7b1b5a7b34438794aed2c178de >> >>>>>> cee1 >> >>>>>>>>> % >> >>>>>>>>> 7C0%7C0%7C636391039781390709&sdata=2zBxDD8UoNESAJZyvKWBerW8U >> iGUFb >> >>>>>> pCHf%2B >> >>>>>>>>> n >> >>>>>>>>> iUgm0aA%3D&reserved=0 >> >>>>>>>>> tp15510p15807.html >> >>>>>>>>> To start a new topic under Apache Flex Users, email >> >>>>>>>>> ml+s2333346n1...@n4.nabble.com >> >>>>>>>>> To unsubscribe from Apache Flex Users, click here >> >>>>>>>>> >> >>>>>>>>> <https://na01.safelinks.protection.outlook.com/?url= >> >>>>>> http%3A%2F%2Fapache- >> >>>>>>>>> f >> >>>>>>>>> lex-users.2333346.n4.nabble.com%2Ftemplate% >> >>>>>> 2FNamlServlet.jtp%3Fmacro%3Du >> >>>>>>>>> n >> >>>>>>>>> >> >>>>>>>>>subscribe_by_code%26node%3D1%26code%3DcHJhc2hha3VtY >> XJAZ21haWwuY29t >> >>>>>> fDF8LT >> >>>>>>>>> U >> >>>>>>>>> 0MTcyMzE2NA&data=02%7C01%7C%7C5d32ae4db4c14fd8227a08d4ea47 >> >>>>>> 6740%7Cfa7b1b5 >> >>>>>>>>> a >> >>>>>>>>> 7b34438794aed2c178decee1%7C0%7C0%7C636391039781390709& >> >>>>>> sdata=u9qzMLM9zEaI >> >>>>>>>>> C >> >>>>>>>>> Vfd8TuFsLmf8Tjcw4G%2BEN6U2Jf35tc%3D&reserved=0==> >> >>>>>>>>> . >> >>>>>>>>> NAML >> >>>>>>>>> >> >>>>>>>>> <https://na01.safelinks.protection.outlook.com/?url= >> >>>>>> http%3A%2F%2Fapache- >> >>>>>>>>> f >> >>>>>>>>> lex-users.2333346.n4.nabble.com%2Ftemplate% >> >>>>>> 2FNamlServlet.jtp%3Fmacro%3Dm >> >>>>>>>>> a >> >>>>>>>>> cro_viewer%26id%3Dinstant_html%2521nabble%253Aemail. >> >>>>>> naml%26base%3Dnabble >> >>>>>>>>> . >> >>>>>>>>> naml.namespaces.BasicNamespace-nabble.view. >> >>>>>> web.template.NabbleNamespace- >> >>>>>>>>> n >> >>>>>>>>> abble.view.web.template.NodeNamespace%26breadcrumbs% >> >>>>>> 3Dnotify_subscribers >> >>>>>>>>> % >> >>>>>>>>> 2521nabble%253Aemail.naml-instant_emails%2521nabble% >> >>>>>> 253Aemail.naml-send_ >> >>>>>>>>> i >> >>>>>>>>> nstant_email%2521nabble%253Aemail.naml&data=02%7C01% >> >>>>>> 7C%7C5d32ae4db4c14fd >> >>>>>>>>> 8 >> >>>>>>>>> 227a08d4ea476740%7Cfa7b1b5a7b34438794aed2c178de >> >>>>>> cee1%7C0%7C0%7C6363910397 >> >>>>>>>>> 8 >> >>>>>>>>> 1390709&sdata=AByKY5e%2BF3ekcVN7l1hKEfp0TkaMEy3p% >> >>>>>> 2BSw7wuHHCzI%3D&reserve >> >>>>>>>>> d >> >>>>>>>>> =0> >> >>>>>>>>> >> >>>>>>>> >> >>>>>>>> >> >>>>>>>> >> >>>>>>>> >> >>>>>>>> ----- >> >>>>>>>> Regards, >> >>>>>>>> Prashant >> >>>>>>>> -- >> >>>>>>>> View this message in context: >> >>>>>>>> https://na01.safelinks.protection.outlook.com/?url= >> >>>>>> http%3A%2F%2Fapache-fl >> >>>>>>>> e >> >>>>>>>> x-users.2333346.n4.nabble.com%2FRemote-object-for-Flex- >> >>>>>> JS-tp15510p15809.h >> >>>>>>>> t >> >>>>>>>> ml&data=02%7C01%7C%7C5d32ae4db4c14fd8227a08d4ea47 >> >>>>>> 6740%7Cfa7b1b5a7b3443879 >> >>>>>>>> 4 >> >>>>>>>> aed2c178decee1%7C0%7C0%7C636391039781390709&sdata= >> >>>>>> OBijYEbbq0BjTiZ44ouvJ9w >> >>>>>>>> a >> >>>>>>>> D4N1Gd49pm0aO36ZGcI%3D&reserved=0 >> >>>>>>>> Sent from the Apache Flex Users mailing list archive at >> >>>>>>>>Nabble.com. >> >>>>>>> >> >>>>>> >> >>>>>> >> >>>> >> >>>> >> >>> >> >>> >> >>> -- >> >>> Carlos Rovira >> >>> http://about.me/carlosrovira >> >>> >> >> >> >> >> >> >> >> -- >> >> >> >> Piotr Zarzycki >> >> >> >> mobile: +48 880 859 557 >> >> skype: zarzycki10 >> >> >> >> LinkedIn: http://www.linkedin.com/piotrzarzycki >> >> <https://pl.linkedin.com/in/piotr-zarzycki-92a53552> >> > >> >> > > > -- > > <http://www.codeoscopic.com> > > Carlos Rovira > > Director General > > M: +34 607 22 60 05 <607%2022%2060%2005> > > http://www.codeoscopic.com > > http://www.avant2.es > > > Conocenos en 1 minuto! <https://youtu.be/P2IEAYDG5HU> > > > 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. > > -- <http://www.codeoscopic.com> Carlos Rovira Director General M: +34 607 22 60 05 http://www.codeoscopic.com http://www.avant2.es Conocenos en 1 minuto! <https://youtu.be/P2IEAYDG5HU> 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.
