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
Ralph Goers wrote:
+1. For one, the cowarp source is now an integral part of the sample
portal (in 2.1) and it makes it harder to deal with being outside of Cocoon.
BTW - what cowarp will 2.1 be using? The one at Sourceforge or at
Cocoon? Perhaps it would be better to share it like
Jörg Heinicke wrote:
Von: Carsten Ziegeler
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
+0 (Deprecating them in 2.1 does not really matter as we have not released 2.2
Carsten Ziegeler wrote:
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 9 Jun 2006, Carsten Ziegeler wrote:
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
Carsten Ziegeler wrote:
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
+0. I never used
