> -----Original Message----- > From: Sylvain Wallez [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 04, 2005 3:22 PM > To: [email protected] > Subject: Re: AJAX and Cocoon - Design Patterns > > .... > > Where Cocoon can shine IMO with Ajax apps is that a website (not > necessarily a webapp) is often split into several > subpipelines that are > aggregated. With Ajax, each of the areas that are normally > aggregated in > a full-page rendering model live their lives separately. What > that means > is that those pipelines that use to be internal-only will now be used > both by the full page rendering (for the first page display > or non-Ajax > browsers) and for individual Ajax updates.
Hmmm, for instance in portals ? I have been thinking about it. Can we let each portlet live its own life using Ajax ? In my portal, I have a portlet that needs updating each minute. Right now I have to update the whole page fo that. Even if the caching stuff helps, but the whole page needs to be sent to the browser. With Ajax that portlet can refresh itself alone:) Maybe someone should make an Ajaxcoplet ? Armaz > > Sylvain > > -- > Sylvain Wallez Anyware Technologies > http://people.apache.org/~sylvain http://www.anyware-tech.com > Apache Software Foundation Member Research & Technology Director > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
