On Mon, Sep 8, 2008 at 1:59 PM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
> Bertrand Delacretaz wrote: >> ...What you suggest sounds good for this, except that we might need an >> additional "priority" property, to be able to resolve conflicts >> without having to ask users. >> > Hmm, actually I've no real opinion here whether this is good or not. > Yes, we could add such a priority property - on the other hand if you > know that you have to set this property, you might also know that you > have to remove the url configuration from another node.... The use case is: -User starts with an "empty" Sling app -> gets default Sling homepage on / -User loads a Sling-based application in the repository -> gets that app's homepage on /, due to higher priority -Use removes Sling-based app -> gets default Sling homepage again. Using vanity URL priorities is not optimal, but it's useful in this case and I'm not sure how to solve it otherwise. -Bertrand
