Hi everyone! ... > > > > 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 ?
Me me me! :D I had the same idea and I wanted to spend some time on that during the Hackathon tomorrow and the day after. Along the lines of www.google.com/ig and www.netvibes.com. Bye! max --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
