[ 
https://issues.apache.org/jira/browse/SYNAPSE-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12658822#action_12658822
 ] 

indika priyantha kumara commented on SYNAPSE-490:
-------------------------------------------------

Hi Hiranya 

States are only in configuration context and calling setProperty and 
getProperty   on it and calling (axis2)Replicator.replicate() explicitly , are 
sufficient for enable replication. Instead of 'getProperty' , it is better to 
use 'getPropertyNonReplicable' as we never want to replicate when looking up 
existing values (only need to replicate after states has been changed - by 
calling setProperty explicitly  and Replicator.replicate). There are some other 
states in Algorithm context do these and can refer those. There is a Replicator 
utility class in synapse too. 

Thanks
Indika

> Add a Field to the AlgorithmContext to Support Storing Algorithm Impl 
> Specific Data
> -----------------------------------------------------------------------------------
>
>                 Key: SYNAPSE-490
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-490
>             Project: Synapse
>          Issue Type: Improvement
>          Components: Endpoints
>    Affects Versions: NIGHTLY
>         Environment: Any
>            Reporter: Hiranya Jayathilaka
>            Assignee: Hiranya Jayathilaka
>            Priority: Minor
>             Fix For: NIGHTLY
>
>
> Currently AlgorithmContext can be used to store only endpoint index values. 
> However this may not be sufficient for custom load balance algorithm 
> implementations. Such implementations may need to store other impl specific 
> data items. Therefore AlgorithmContext should have a map of parameters and 
> get-set methods to manipulate the parameters.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to