[
https://issues.apache.org/jira/browse/FLEX-33881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814799#comment-13814799
]
Maurice Amsellem commented on FLEX-33881:
-----------------------------------------
Sorry, I overlooked your anwser.
You say you have seen it used in several apps.
Do you remember in what situations?
Then in this case, it's too risky to break the existing behavior.
Since there is a simple "workaround", we could just close the ticket
> Change AbstractInvoker to not store last call result by default
> ---------------------------------------------------------------
>
> Key: FLEX-33881
> URL: https://issues.apache.org/jira/browse/FLEX-33881
> Project: Apache Flex
> Issue Type: New Feature
> Components: RPC: RemoteObject
> Affects Versions: Apache Flex 4.9.0, Apache Flex 4.10.0, Apache Flex 4.11.0
> Reporter: Maurice Amsellem
> Priority: Minor
>
> *Context:*
> AbstractInvoker is the superclass of all async operation
> (RemoteOperation,HttpService, etc.).
> It always stores by default the result of the last call, than can then be
> accessible through its lastResult property.
> This means the last call result won't be garbage collected, unless
> clearResult() is called explicitly.
> This can be an issue if the remote operation is called one or rarely, and
> returns large result (Typically, remote operations that are called at
> application startup to load configuration data).
> *Request:*
> Since lastResult property is not really useful, as results are normally
> processed in the result handlers, it would be better if storing the last
> call's result becomes an option, and be turned OFF by default.
> *Benefits:*
> Large results are garbage collected by default, without having to manually
> call clearResult()
--
This message was sent by Atlassian JIRA
(v6.1#6144)
