flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maurice Amsellem (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FLEX-33881) Change AbstractInvoker to not store last call result by default
Date Wed, 06 Nov 2013 10:51:17 GMT

     [ https://issues.apache.org/jira/browse/FLEX-33881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Maurice Amsellem updated FLEX-33881:
------------------------------------

    Description: 
*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()

  was:
AbstractInvoker is the superclass of all async operation (RemoteOperation,HttpService, etc.).
It will store by default the result of the last call, than can then be accessible through
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 very large
results (Typically, remote operations that are called at application startup).
Since lastResult property is not really useful, as results are normally processed in the result
handlers, it would be better if storing the last result call *becomes an option, and be turned
OFF by default*

Benefits:
large results are garbage collected by default, without having to manually call clearResult()


> 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)

Mime
View raw message