Jean-Christophe Kermagoret wrote: > Waouuuuhhhhhh > > Thanks for this quick reply :-) > > I'm interested to try this layout to compare the costs between (one > coplet update) and (one coplet update + reload of the rest of the portal). > > Do you think it's worth the case ? > > Do you know if somebody already worked on this ? The idea is to build a > AJAX layout to minimize reloading if it permits to spare cpu cycles and > networkbandwith > > WDYT ? > Have a look at the portal in Cocoon trunk :) Especially at the Gallery demo - for minimizing/maximizing and some updates of coplets, the refresh is done using ajax and only the affected coplet is transfered from the server to the client. The work is not finished yet which means there are still cases where Ajax is not used but could be used. But in general I think it's worth to think about this.
Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
