From dev-return-105739-archive-asf-public=cust-asf.ponee.io@sling.apache.org Thu Apr 16 09:42:02 2020 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 03E35180638 for ; Thu, 16 Apr 2020 11:42:01 +0200 (CEST) Received: (qmail 67693 invoked by uid 500); 16 Apr 2020 09:42:01 -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 67676 invoked by uid 99); 16 Apr 2020 09:42:01 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Apr 2020 09:42:01 +0000 Received: from jira-he-de.apache.org (static.172.67.40.188.clients.your-server.de [188.40.67.172]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 9A879E2569 for ; Thu, 16 Apr 2020 09:42:00 +0000 (UTC) Received: from jira-he-de.apache.org (localhost.localdomain [127.0.0.1]) by jira-he-de.apache.org (ASF Mail Server at jira-he-de.apache.org) with ESMTP id 1B267780425 for ; Thu, 16 Apr 2020 09:42:00 +0000 (UTC) Date: Thu, 16 Apr 2020 09:42:00 +0000 (UTC) From: "Julian Sedding (Jira)" To: dev@sling.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (SLING-9365) Optimize servlet to resource provider servlet mounter MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SLING-9365?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1708= 4711#comment-17084711 ]=20 Julian Sedding commented on SLING-9365: --------------------------------------- [~karlpauls] oh sorry for the noise. Obviously I didn't read the ticket car= efully enough. Glad that the ResourceDecorator idea may be of help! > Optimize servlet to resource provider servlet mounter > ----------------------------------------------------- > > Key: SLING-9365 > URL: https://issues.apache.org/jira/browse/SLING-9365 > Project: Sling > Issue Type: Improvement > Components: Scripting > Affects Versions: Servlets Resolver 2.6.4 > Reporter: Karl Pauls > Assignee: Karl Pauls > Priority: Major > Fix For: Servlets Resolver 2.6.6 > > > The current ServletMounter creates a resource provider for each registere= d servlet. That works fine for a given amount of servlets but can become pr= oblematic for a high number of servlets as it means that on the one hand, t= he number of services is doubled and on the other hand, a lot of notificati= ons are send out as well as a lot of computation has to be done by the reso= urce resolver.=C2=A0 > As an optional remedy for these kinds of scenarios, we should allow to co= nfigure the mounter to instead provide a single resource provider that has = manages the servlets internally. -- This message was sent by Atlassian Jira (v8.3.4#803005)