From dev-return-92902-archive-asf-public=cust-asf.ponee.io@sling.apache.org Tue Oct 23 19:32:47 2018 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 [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 4C0C318066B for ; Tue, 23 Oct 2018 19:32:47 +0200 (CEST) Received: (qmail 92371 invoked by uid 500); 23 Oct 2018 17:32:46 -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 92360 invoked by uid 99); 23 Oct 2018 17:32:46 -0000 Received: from mail-relay.apache.org (HELO mailrelay1-lw-us.apache.org) (207.244.88.152) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Oct 2018 17:32:46 +0000 Received: from auth1-smtp.messagingengine.com (auth1-smtp.messagingengine.com [66.111.4.227]) by mailrelay1-lw-us.apache.org (ASF Mail Server at mailrelay1-lw-us.apache.org) with ESMTPSA id 8F7B1205 for ; Tue, 23 Oct 2018 17:32:45 +0000 (UTC) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailauth.nyi.internal (Postfix) with ESMTP id 2691021EA7 for ; Tue, 23 Oct 2018 13:32:45 -0400 (EDT) Received: from web2 ([10.202.2.212]) by compute5.internal (MEProxy); Tue, 23 Oct 2018 13:32:45 -0400 X-ME-Sender: X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 99) id CF1E762278; Tue, 23 Oct 2018 13:32:44 -0400 (EDT) Message-Id: <1540315964.1683550.1552008944.20354B4A@webmail.messagingengine.com> From: Jason E Bailey To: dev@sling.apache.org MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-b315a288 In-Reply-To: Subject: Re: Sling 12 themes References: <92538ad56814f23181c631a73e58667fa54cfc37.camel@apache.org> <1540310562.1656839.1551894136.28C1EEB6@webmail.messagingengine.com> <1540312928.1668473.1551939448.04720B8D@webmail.messagingengine.com> <5180b73f-7f2a-2184-5f11-8ff36a99ef3e@apache.org> <1540313985.1674332.1551959696.720E31E5@webmail.messagingengine.com> Date: Tue, 23 Oct 2018 13:32:44 -0400 On Tue, Oct 23, 2018, at 1:24 PM, Konrad Windszus wrote: > I would rather prefer to get rid of a server side postprocessing like=20 > the rewriter. For HTL I agree with Carsten, we should probably look into= =20 > a generic link rewriting mechanism which allows for custom rewriting=20 > with a nice HTL plugin. Much less overhead than a Cocoon pipeline which=20 > needs to deserialize and then serialize again... > Would be interesting to get forward in that regard with Sling 12.=20 There is a real world need for html post processing that is not dependent o= n HTL. The rewriter is already not a core component and something that is c= ommunity supported so I don't think enhancing it should be much of an issue= . For what it's worth though I don't like the overhead of the existing pipe= line as it is anyway. HTML doesn't have anything to do with XML anymore. =20 > For JSON and client side rendering the link rewriting must be rather=20 > encapsulated on the client side as well. I don=E2=80=99t think Sling shou= ld=20 > provide that functionality as Sling is focusing on the server side. Missing a point here I think. If you are focusing on link rewriting, that i= s something that can only occur on the server side. Helps with multi-tenan= cy and cross linking.