I guess I still don't understand. Is the goal to expose the responseData? Why does the bead need to record the response data? Why can't it just get it when someone asks for it?
I'm by no means an expert on Aspects. I think beads should be able to do some of what I understand aspects do without modifying the class definition. If the strand doesn't hide stuff from the beads (by storing data in a model) beads should have access to enough stuff from the strand, and thus additional beads can expose that data. Thanks, -Alex On 7/11/17, 10:28 PM, "yishayw" <yishayj...@hotmail.com> wrote: >See upthread my response to Pitor > > >> I was thinking the same thing but it’s complicated to make it into a >>bead. >> It would have to catch the ‘complete’ event and record the response data >> before anyone else does. Since we don’t have event listener priorities I >> don’t know how to do that. I hope to update the wiki Greg wrote when I’m >> done with this. Maybe I can pass on some of my experiences. > > > > > >-- >View this message in context: >https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle >x-development.2333347.n4.nabble.com%2FRe-git-commit-flex-asjs-refs-heads-d >evelop-Add-FileUploaderWithResponseData-tp63051p63136.html&data=02%7C01%7C >%7Cd06b2ce9fd704a05c4a508d4c8e98cbd%7Cfa7b1b5a7b34438794aed2c178decee1%7C0 >%7C0%7C636354352800533854&sdata=9agjvr89lTGBZB7RzDDMA6S4A3cGd0CGSowI9T7Gb8 >k%3D&reserved=0 >Sent from the Apache Flex Development mailing list archive at Nabble.com.
