[jira] [Comment Edited] (SLING-3505) Improve handling of updates to mapping (alias, vanity path)

["Antonio Sanso (JIRA)" <ji...@apache.org>]

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

Antonio Sanso edited comment on SLING-3505 at 6/23/14 12:25 PM:
----------------------------------------------------------------

attaching patch that try to address the vanityOrder. [~justinedelson] may you please give a  look into :) ?


was (Author: asanso):
attaching patch that try to address the vanityOrder

> Improve handling of updates to mapping (alias, vanity path)
> -----------------------------------------------------------
>
>                 Key: SLING-3505
>                 URL: https://issues.apache.org/jira/browse/SLING-3505
>             Project: Sling
>          Issue Type: Improvement
>          Components: ResourceResolver
>    Affects Versions: Resource Resolver 1.1.0
>            Reporter: Carsten Ziegeler
>            Assignee: Antonio Sanso
>         Attachments: SLING-3505-patch.txt, SLING-3505-patch2.txt, SLING-3505-patch2.txt, SLING-3505-patch3.txt
>
>
> The update handling for the mapping including aliases and vanity path is a simple algorithm which simply updates the whole mapping. Especially with large mapping info spread across the repository, a simple update of a single property results in the whole mapping info to be recreated.
> It would be great if this could be improved.
> Right now, only the active mapping is hold in memory - as a change of a single property might cause to activate a totally different mapping than the one which was changed (e.h. when the ordering is changed), the update needs to be more complex or more information needs to be hold in memory.
> In addition there is more to consider, like if the vanity path info is changed, only the new value is available - but the old is gone.



--
This message was sent by Atlassian JIRA
(v6.2#6252)