From dev-return-85332-archive-asf-public=cust-asf.ponee.io@sling.apache.org Fri Jan 12 15:46:02 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 0174B180621 for ; Fri, 12 Jan 2018 15:46:02 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id E5707160C33; Fri, 12 Jan 2018 14:46:01 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 5E125160C30 for ; Fri, 12 Jan 2018 15:46:01 +0100 (CET) Received: (qmail 9224 invoked by uid 500); 12 Jan 2018 14:46:00 -0000 Mailing-List: contact dev-help@sling.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@sling.apache.org Delivered-To: mailing list dev@sling.apache.org Received: (qmail 9212 invoked by uid 99); 12 Jan 2018 14:46:00 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Jan 2018 14:46:00 +0000 Received: from mail-wm0-f47.google.com (mail-wm0-f47.google.com [74.125.82.47]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id C559A1A00E6 for ; Fri, 12 Jan 2018 14:45:58 +0000 (UTC) Received: by mail-wm0-f47.google.com with SMTP id 81so2705830wmb.1 for ; Fri, 12 Jan 2018 06:45:58 -0800 (PST) X-Gm-Message-State: AKwxytfG6EonsI+EYWfRisWyt8n1zU/a/lS6Wdt3gmHU+ewJbqWB13di MKAjvx5h2TmKBMpmA8yqOMc6DA6d31jECnIWtNQ= X-Google-Smtp-Source: ACJfBovxJsjw77iJhqsnyQIr7zpPl86XURix+sfqldpP4mhJlAi50Jfm/i5j+dDuNo82WT0twRBaoOAz4WzMnpV1RA8= X-Received: by 10.28.91.10 with SMTP id p10mr4439189wmb.112.1515768355971; Fri, 12 Jan 2018 06:45:55 -0800 (PST) MIME-Version: 1.0 Received: by 10.28.198.132 with HTTP; Fri, 12 Jan 2018 06:45:55 -0800 (PST) In-Reply-To: <7dc3db96-9d4c-1e5a-f1db-f6ef077650dc@apache.org> References: <13D3B7AD-70C9-4601-8357-F575297B3EF9@gmx.de> <00C07092-AA61-4D82-9A29-E5522333BB75@gmx.de> <7dc3db96-9d4c-1e5a-f1db-f6ef077650dc@apache.org> From: Bertrand Delacretaz Date: Fri, 12 Jan 2018 15:45:55 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Search for specific resource types To: dev Cc: Konrad Windszus Content-Type: text/plain; charset="UTF-8" On Fri, Jan 12, 2018 at 3:25 PM, Carsten Ziegeler wrote: > ...I think some time ago we discussed a separate resource type mgmt service > (which also could cache resource type resolution).... This is similar to my proposal to create a ResourceProvider that exposes the resource type hierarchy. But that was just a quick idea, it's quite possible that we need more functionality in a resource type management service. I would prefer avoiding making changes that complexify the ResourceResolver, if we can. -Bertrand