From dev-return-93675-archive-asf-public=cust-asf.ponee.io@sling.apache.org Mon Nov 12 15:13:55 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 5D307180660 for ; Mon, 12 Nov 2018 15:13:55 +0100 (CET) Received: (qmail 99834 invoked by uid 500); 12 Nov 2018 14:13:54 -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 99822 invoked by uid 99); 12 Nov 2018 14:13:54 -0000 Received: from mail-relay.apache.org (HELO mailrelay2-lw-us.apache.org) (207.244.88.137) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Nov 2018 14:13:54 +0000 Received: from auth2-smtp.messagingengine.com (auth2-smtp.messagingengine.com [66.111.4.228]) by mailrelay2-lw-us.apache.org (ASF Mail Server at mailrelay2-lw-us.apache.org) with ESMTPSA id 8190E2116 for ; Mon, 12 Nov 2018 14:13:53 +0000 (UTC) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailauth.nyi.internal (Postfix) with ESMTP id 2F1E02216F for ; Mon, 12 Nov 2018 09:13:53 -0500 (EST) Received: from web2 ([10.202.2.212]) by compute5.internal (MEProxy); Mon, 12 Nov 2018 09:13:53 -0500 X-ME-Sender: X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 99) id A29BC622C6; Mon, 12 Nov 2018 09:13:52 -0500 (EST) Message-Id: <1542032032.1914458.1574001632.50B5A867@webmail.messagingengine.com> From: Jason E Bailey To: dev@sling.apache.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-c0552f07 Date: Mon, 12 Nov 2018 09:13:52 -0500 Subject: Re: [RT] Simple File System Resource Provider In-Reply-To: <40ec47b6-6635-8655-77c7-65ea5697fe65@apache.org> References: <40ec47b6-6635-8655-77c7-65ea5697fe65@apache.org> +1 on a simple resource provider, I'm curious about the focus on a filesystem provider. I've started playing around with creating one and I see a clear logical association between what a resource provider needs and a key-value store. Good key-value stores already have versioning, and non blocking read and writes. Things that are architecturally nice to have removed from our hands. Something like mvstore - http://www.h2database.com/html/mvstore.html or lmdb - https://symas.com/lmdb/ would be really good to build on. - Jason On Sun, Nov 11, 2018, at 4:55 AM, Carsten Ziegeler wrote: > I've recently tried to run a minimal Sling without JCR. Obviously you > need at least one resource provider to have some content, so I picked > the easiest choice, the file system resource provider. > > However, it turned out that this is not the easiest choice for this > scenario as it has a lot of features, especially support for handling > content XML files and vault files, which again brings in the whole > dependency list to jcr related bundles. In my case I just want to stream > binaries and json files, so none of the above is needed. But still I > need to deploy all the bundles. In addition there are other things like > the json parsing library is embedded in the bundle etc. > > Now, I think we should really have a simple file system resource > provider which only does the basics and has not an endless list of > bundles. I see two ways to get there: make the current provider > extensible and provide all this extra cruft as extensions or write a new > simple provider. > > Thoughts? > > Regards > Carsten > -- > Carsten Ziegeler > Adobe Research Switzerland > cziegeler@apache.org