[ 
https://issues.apache.org/jira/browse/ARIES-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16361082#comment-16361082
 ] 

ASF subversion and git services commented on ARIES-1778:
--------------------------------------------------------

Commit d5bfc3769bb3ed501f41927766a0b9d02ebd3a70 in aries-rsa's branch 
refs/heads/master from [~ch...@die-schneider.net]
[ https://git-wip-us.apache.org/repos/asf?p=aries-rsa.git;h=d5bfc37 ]

[ARIES-1778] Improved naming and documentation


> Use endpoint id as path in zookeeper
> ------------------------------------
>
>                 Key: ARIES-1778
>                 URL: https://issues.apache.org/jira/browse/ARIES-1778
>             Project: Aries
>          Issue Type: Improvement
>          Components: Remote Service Admin
>    Affects Versions: rsa-1.11.0
>            Reporter: Christian Schneider
>            Assignee: Christian Schneider
>            Priority: Major
>             Fix For: rsa-1.12.0
>
>
> Currently we use a quite complicated and not completely correct way to create 
> zookeeper nodes for endpoints.
> Below the base path we use the fully qualified interfacename and below the 
> endpoint id as path. 
> This creates several problems:
>  * To listen to changes we need to create nodes in zookeeper for every 
> interface that is requested as a service. So we end up with many nodes for 
> non remote services.
>  * As an endpoint may have more than one interface we then end up with more 
> than once endpoint for it in zookeeper. When the endpoint changes this 
> results in multiple change events created
> So I propose to change this to a much simpler scheme by simply using the 
> endpoint id as a path in zookeeper. This will make it much easier to listen 
> to changes and also will cause less nodes to be created in zookeeper.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to