Garner Andrews wrote:
I notice on the main portal page that it says under status: "Future
development areas include improved caching and clustering support, further
AJAX integration, new portlet applications, WSRP support, better design and
use experience."

Is there any specific page or discussion on the details of these?  I've not
found anything yet on the site, and through what I've browsed in our mail
archives.  I'd specifically like to know where Jetspeed2 stands on caching
can clustering, AJAX, and WSRP right now.


These are the main development areas for 2.1 release, although with some re-prioritization of late. For one, we don't currently have any developer interested in championing the WSRP cause that I know of. AJAX and a Web2 architecture is where I see the majority of development being done in 2.1-dev. In the 2.0 release, we already have an AJAX XML API for portal customization http://portals.apache.org/jetspeed-2/guides/guide-ajax-api.html

and a little demo of the new direction Jetspeed will be taking for portal customization: client-side AJAX manipulation of the portal model. Additionally, we are prototyping ways to directly integrate AJAX into the portlet API paradigm.

For the server side, our architecture has matured and we are comfortable with what we have there. The final push is to complete the clustering and caching work for the page manager and other critical data structures in the 2.1 release.

Before any of this starts, we are prototyping a new build with Maven-2 and trying to better meet the needs of different configurations of the Jetspeed components. We believe Maven-2 will lend itself much better to custom configurations. I think its a very exciting and critical time for the growth of the Jetspeed-2 portal. We've learned from some mistakes, especially in the build and configuration area. I think its a great opportunity to get involved now and contribute in one of these future areas


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to