From dev-return-87805-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org Sun Jun 11 09:26:55 2006 Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 83991 invoked from network); 11 Jun 2006 09:26:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 11 Jun 2006 09:26:54 -0000 Received: (qmail 45529 invoked by uid 500); 11 Jun 2006 09:26:52 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 45493 invoked by uid 500); 11 Jun 2006 09:26:52 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@cocoon.apache.org List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 45482 invoked by uid 99); 11 Jun 2006 09:26:52 -0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received: from [209.237.227.194] (HELO [127.0.0.1]) (209.237.227.194) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 11 Jun 2006 02:26:51 -0700 Message-ID: <448BE1C6.7000101@apache.org> Date: Sun, 11 Jun 2006 11:26:30 +0200 From: Carsten Ziegeler User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: [Vote] Cowarp, auth-fw and session-fw in 2.2 References: <44894DD1.8070907@apache.org> In-Reply-To: <44894DD1.8070907@apache.org> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Carsten Ziegeler schrieb: > Ok, lets see what others think about it. > > Now, we already discussed this topic a little bit in [1]: > Cocoon contains the auth-fw block which is a modular authentication > framework which can be integrated in your app. It is based on the > session-fw and for example it can be used out of the box in the portal. > Both, session-fw and auth-fw were developed six years ago with the > mindset that everything is XML - during the years, the way of developing > web apps with Cocoon has changed and therefore there are better > alternatives for these blocks, for example the template block and flow. > > In addition I started a replacement for the auth-fw some time ago which > I called CoWarp and which is hosted at sf right now. I had several > reasons for starting this there and not here which are outlined in [1]. > > My main reason is the community aspect. I would like to have a community > first, before moving the code here. Now, in fact neither the session-fw > nor the auth-fw have a real community here, so perhaps this reason is a > little bit obsolete in *this case*. > > As both, auth-fw and session-fw are really out dated and as cowarp is a > better implementation of the auth-fw, I propose to: > a) deprecate auth-fw and session-fw in 2.1.x > b) remove auth-fw and session-fw in 2.2 > c) add cowarp as an own block to 2.2 > +1 Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/