[SLIDER-60] have a naming policy that handles users and app instances

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Component/s: registry
• Sprint: slider may 1, slider may 2, slider June 1, slider June 2, Slider July #1, Slider August #1
• Assignee: Unassigned
• Reporter: Steve Loughran
• Created: 15/May/14 13:08
• Updated: 04/Aug/14 18:44
• Resolved: 04/Aug/14 18:44

Description

we need a consistent and sensible policy for handling registry entries belonging to different users, as the simple application name isn't enough -we allow different users to create applications with the same name (more precisely: we have to).

The RegistryNaming naming class implements the policy here, currently $user-$instance -is it what we want?

we could have a more hierarchical view of the registry, of

registry/user/servicetype/appname

and permissions could hide/view based on the user