Implemented as designed: https://issues.apache.org/jira/browse/FLEX-33881
Will be available in next nightly build... -----Message d'origine----- De : Maurice Amsellem [mailto:[email protected]] Envoyé : jeudi 7 novembre 2013 10:51 À : [email protected]; [email protected] Objet : RE: RemoteOperation last result not garbage collected >Isn't it true that lastResult is used in binding expressions which is why it >has to be "sticky? > And don't you normally have references to data from the lastResult around in > your app until the next invocation? I understand now: this is the MXML way of handling RemoteObject operation results, in very simple cases. I am doing everything in ActionScript using result Handlers to have better control. >But also, what could possibly break if you add a flag and default it to the >old behavior? If nothing, feel free to add it. Will do. -----Message d'origine----- De : Alex Harui [mailto:[email protected]] Envoyé : jeudi 7 novembre 2013 06:12 À : [email protected]; [email protected] Objet : Re: RemoteOperation last result not garbage collected Isn't it true that lastResult is used in binding expressions which is why it has to be "sticky? And don't you normally have references to data from the lastResult around in your app until the next invocation? But also, what could possibly break if you add a flag and default it to the old behavior? If nothing, feel free to add it. -Alex On 11/6/13 4:40 AM, "Maurice Amsellem" <[email protected]> wrote: >I am not an expert of the matter, but since this behavior is >implemented in AbstractInvoker, which is the base class of all remote >application, then I guess it applies. >You can easily check by yourself... > >Maurice > >-----Message d'origine----- >De : Paul Hastings [mailto:[email protected]] Envoyé : mercredi 6 >novembre 2013 13:27 À : [email protected] Objet : Re: >RemoteOperation last result not garbage collected > >On 11/6/2013 8:05 AM, Maurice Amsellem wrote: >> I discovered a not-so-known behavior of RemoteObject that could be >>useful to the community: >> >> RemoteObject RemoteOperations are keeping a reference to the last >>call result, that can be retrieved through lastResult property. >> Most of the time, you don't need that reference, as you will be >>processing the result in the result handlers. > >interesting find. we have some apps that make a bunch of REST calls to >ESRI's arcGIS server & i guess this would be applicable. > >but does this apply to all remoting calls? what about to/from >coldfusion or blazeDS? we've only ever cared about ResultEvents from >these & never bothered w/tokens. > >
