Hey Esther, Esther Fuldauer a écrit : > I was thinking more of another case I have where I need to update the > html each time the page gets loaded. If the pieces I need to rotate on > the page are more than 20, how do you suggest I go about it? Also an > html for each piece?
It really depends on the semantics of your bits. I mean, eventually they're HTML in the page. So how are they represented originally? Are those static XHTML fragments? If yes, don't bother: get them! If you worry about the 2-resource-per-domain HTTP recommendation, you may decide to concatenate them in a file with delimiters, fetch the whole thing, split client-side (String.split is there for you), and do updates yourself instead of using Ajax.Updater (e.g. use Ajax.Request with a custom onSuccess callback that splits, then loops over fragments and containers and calls update manually). The short point is: if there is no *compelling* reason to use something else than HTML for your fragments, then *go HTML*. Actually, go XHTML (no ambiguity makes for faster, more reliable parsing and DOM building by the browser). -- Christophe Porteneuve aka TDD [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
