Return-Path: X-Original-To: apmail-sling-dev-archive@www.apache.org Delivered-To: apmail-sling-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BFC63FAB4 for ; Tue, 1 Oct 2013 16:42:53 +0000 (UTC) Received: (qmail 8842 invoked by uid 500); 1 Oct 2013 16:42:53 -0000 Delivered-To: apmail-sling-dev-archive@sling.apache.org Received: (qmail 8798 invoked by uid 500); 1 Oct 2013 16:42:53 -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 8790 invoked by uid 99); 1 Oct 2013 16:42:52 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Oct 2013 16:42:52 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ianboston@gmail.com designates 209.85.212.171 as permitted sender) Received: from [209.85.212.171] (HELO mail-wi0-f171.google.com) (209.85.212.171) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Oct 2013 16:42:46 +0000 Received: by mail-wi0-f171.google.com with SMTP id hm2so5883911wib.4 for ; Tue, 01 Oct 2013 09:42:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=XZalYZupOHvSt/bQIiA9/dwJcMOuUjBHs0pTZq8CQ2g=; b=tdPl4ckXq3u0pk3l4TFs8ISazWNLk99717G1aXxaaGbNigiH4IpD8mhYRxRrzZQ3Q3 vAgdT7NVAt+qrxAv/jnFtd3Z7F0XSH1RBXQPVhJGlBjj4Htc1kKph3caTXbHeIYoWP0Q leIdaeMKjCpTmhBqS8D48rC2Nn3Z43tK5vGmyG1LqLbScT/LdCkxnpkB7LhAjSWWDFVX Q3QV9YGJFN94lelaQHbL1wWyf49hkvj4O9SyERYoZycnOmoltdhouOLx5DQdK1SHpcLm lAj4T4IDg027zQaTR27aXL/hTLqxpJz1PZP55XqkQEVlu0KSZ21Mr6pChkbNuY/yB1MF 64Hg== MIME-Version: 1.0 X-Received: by 10.194.178.166 with SMTP id cz6mr2628862wjc.53.1380645745848; Tue, 01 Oct 2013 09:42:25 -0700 (PDT) Sender: ianboston@gmail.com Received: by 10.217.43.200 with HTTP; Tue, 1 Oct 2013 09:42:25 -0700 (PDT) In-Reply-To: References: Date: Tue, 1 Oct 2013 17:42:25 +0100 X-Google-Sender-Auth: ZRti_ojY77uX0Ss8P9_4_h8YnPY Message-ID: Subject: Re: Apache Cassandra backend for Sling: GSoC2013 Project From: Ian Boston To: "dev@sling.apache.org" Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Hi Dishara, Congratulations, you achieved everything you set out to and showed a real willingness to work with the Sling community, which for all those that know the Apache way is possibly more important than rock star coding. I am sure that others will build on what you have discovered and created. Should you find that you want to continue working on Sling with the community in the coming months your contributions will be welcomed. Finally, good luck in your continuing student life and if this year was your final year, best of luck in your finals. Best Regards Ian On 1 October 2013 04:25, Dishara Wijewardana wrote: > Hi Ian and all, > Got to know that I have successfully passed the GSoC 2013 which was a my > dream. Thank you all for helping me through all the time and making it true > . I also uploaded the code to Google. > > Thanks again, > > > > On Thu, Apr 25, 2013 at 12:59 AM, Dishara Wijewardana < > ddwijewardana@gmail.com> wrote: > >> >> >> On Wed, Apr 24, 2013 at 4:38 AM, Ian Boston wrote: >> >>> On Wednesday, April 24, 2013, Dishara Wijewardana wrote: >>> >>> > On Tue, Apr 23, 2013 at 3:59 AM, Ian Boston > >>> > wrote: >>> > >>> > > Hi Dishara, >>> > > The diagram looks good and summarises how resource providers are >>> > integrated >>> > > into the resources resolver. Obviously there is a little more detail >>> in >>> > > reality, but its a good overview. >>> > > >>> > Thanks Ian for the feedback. >>> > With that diagram I have just submitted my one and only GSoC 2013 >>> project >>> > proposal to Google ;-). >>> >>> >>> Good. >>> Don't forget to state that this is your only GSoC 2013 submission in the >>> proposal, and to declare if you will be doing anything other than your >>> studies during the time period. Of importance are other part time jobs, >>> studies and exams. Part time jobs are not allowed by GSoC which requires >>> your full attention. Studies and exams clashing with the GSoC timescales >>> are an unfortunate feature of the GSoC programme being based on the US >>> academic year. I have worked with students who were also doing finals, and >>> managed to achieve excellent project outcomes, (and an outstanding final >>> degree result) but any conflicts need to be declared up front, so that the >>> mentor and the student can plan around them. If your studies are active >>> during GSoC then you should also let your academic staff know that you are >>> taking part. >>> >>> If you could declare that information in the proposal, including if there >>> are no conflicts, then they will strengthen your proposal. >>> >>> Hi Ian, >> Completely agree. Really useful instructions. I have mentioned those facts >> in the proposal and updated it. >> Thank you. >> >> >> >>> Best regards >>> Ian >>> >>> >>> >>> >>> > >>> > > >>> > > Ian >>> > > >>> > > On Tuesday, April 23, 2013, Dishara Wijewardana wrote: >>> > > >>> > > > Hi Ian, >>> > > > Here [1] I have attached the high level architecture diagram of the >>> > > > cassandra back end implementation for Sling to the JIRA. Please let >>> me >>> > > know >>> > > > if there is any concerns so that I can use this diagram to the >>> > proposal. >>> > > > >>> > > > [1] - >>> > > > >>> > > > >>> > > >>> > >>> https://issues.apache.org/jira/secure/attachment/12579842/Sling%20Cassandra%20backend%20Architecture.jpg >>> > > > >>> > > > On Sat, Apr 13, 2013 at 4:29 PM, Ian Boston wrote: >>> > > > >>> > > > > Hi, >>> > > > > The breakdown looks good, but I think you should aim to keep the >>> > > > > implementation in Cassandra simple to start with and not >>> > underestimate >>> > > > how >>> > > > > much time it may take to implement both read/write and access >>> control >>> > > on >>> > > > > read/write. No need to change the plan or be too specific at this >>> > > stage. >>> > > > > >>> > > > > Best Regards >>> > > > > Ian >>> > > > > >>> > > > > >>> > > > > On 12 April 2013 23:24, Dishara Wijewardana < >>> ddwijewardana@gmail.com >>> > > >>> > > > > wrote: >>> > > > > >>> > > > > > Hi Ian, >>> > > > > > I am in the process of writing the proposal. So as you mentioned >>> > > > earlier >>> > > > > it >>> > > > > > is better to split this in to 4 sub tasks and 2 before midterm >>> and >>> > 2 >>> > > > > after >>> > > > > > mid term. >>> > > > > > >>> > > > > > So in summary I would like to add the subtasks that I feel. >>> Please >>> > > add >>> > > > > > anything I am missing or anything required to have. >>> > > > > > >>> > > > > > Main tasks overview: >>> > > > > > 1. Implementing a CassandraResourceProvider to READ from >>> > Cassandra. >>> > > > > > Implementation Details [1] >>> > > > > > 2. Test with one node Cassandra cluster end to end with the >>> > > > > implementation >>> > > > > > of #1. >>> > > > > > 3. Enhance CassandraResourceProvider to READ with access control >>> > > (with >>> > > > > > latest security related APIs). >>> > > > > > 4. Enhance CassandraResourceProvider(or may be a new interface >>> for >>> > > > > writing >>> > > > > > i.e CassandraPopulator) to WRITE and WRITE with access control. >>> > > > > > >>> > > > > > Here as I feel, #1 and #2 completion will more weight and >>> > relatively >>> > > > more >>> > > > > > time consuming than #3 and #4 (I am not aware of the complexity >>> of >>> > > > > > incoperating the access control to READ/WRITE). >>> > > > > > >>> > > > > > Appreciate your valuable feedback on this, whether this task >>> > > breakdown >>> > > > is >>> > > > > > appropriate or not suits to the GSoC time line or anything more >>> to >>> > > > > > add/remove and etc ? >>> > > > > > >>> > > > > > [1] : Implementation Details: >>> > > > > > >>> > > > > > - Write a CassanrdaResourceProviderUtil which is basically a >>> > > cassendra >>> > > > > > client which will facilitate all cassandra related operations >>> > > required >>> > > > by >>> > > > > > other modules (CassandraResourceProvider and >>> > > > CassandraResourceResolver). >>> > > > > > >>> > > > > > - Implementation of CassandraResourceProvider >>> > > > > > >>> > > > > > - Implementation of CassandraResourceResolver >>> > > > > > >>> > > > > > - Implementation of CassandraResource >>> > > > > > >>> > > > > > >>> > > > > > On Sun, Apr 7, 2013 at 3:27 PM, Ian Boston >>> wrote: >>> > > > > > >>> > > > > > > On 7 April 2013 14:07, Dishara Wijewardana < >>> > > ddwijewardana@gmail.com> >>> > > > > > > wrote: >>> > > > > > > >>> > > > > > > > On Sun, Apr 7, 2013 at 3:00 AM, Ian Boston >>> > > wrote: >>> > > -- >>> > Thanks >>> > /Dishara >>> > >>> >> >> >> >> -- >> Thanks >> /Dishara >> > > > > -- > Thanks > /Dishara