You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by "Ross Gardler (JIRA)" <ji...@apache.org> on 2005/08/13 12:37:54 UTC
[jira] Commented: (FOR-626) Reusing Cocoon Portal Engine
[ http://issues.apache.org/jira/browse/FOR-626?page=comments#action_12318707 ]
Ross Gardler commented on FOR-626:
----------------------------------
Some discussion:
http://marc.theaimsgroup.com/?t=112282648300002&r=1&w=2
> Reusing Cocoon Portal Engine
> ----------------------------
>
> Key: FOR-626
> URL: http://issues.apache.org/jira/browse/FOR-626
> Project: Forrest
> Type: Improvement
> Components: Views
> Versions: 0.8-dev
> Reporter: Gavin
>
> A couple of the Forrest devs attended a talk on the Cocoon Portal engine
> and came away feeling that we should explore leveraging *parts* of this
> engine in the views implementation. I can see there are a few strong
> cases for this, the most significant are:
> (NOTE: I (Ross) did not attend the presentation but I have said a few times
> that we should look at the Cocoon Portal, so I have some sypathies with
> this perspective):
> - The portal engine does what Views is intended to do. It adds more than
> views needs (such as authentication), but since it is modular we should
> be able to reuse what we need.
> - The technique for configuring the portal (or view) has been developed
> over a period of time and is in use on some excellent sites. In fact the
> config stuff is one of the major things that changed in the second
> release of the portal code. In other words, it is more mature.
> This was not discussed at the views workshop, and so the implications
> have not been fully explored. This will require some considerable thought.
> This issue is the result of an ApacheCon discussion, more, including links to the original ApacheCon Summaries at :-
> http://issues.apache.org/jira/browse/FOR-618 "Create issues for items discussed at Apachecon"
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira