>Correct me if I'm wrong, but Tiles is, in essence, just the JSP include >extended a bit. So, if I have a page with 3 tiles (or 3 JSP includes >alternatively), what gets returned to the browser is still a single HTML >document that is the result of inserting the 3 tiles in the main page. > Absolutely right. The difference between JSP includes and Tiles is that Tiles uses a different way to manage inclusions (with tiles-defs.xml or particular jsp tags), because the "main page" can be a simple placeholder to insert a definition via jsp or tiles-defs.xml for layout page and inner pages, or even could not exist at all (e.g. when you refer to Tiles definitions only in action forwards).
> >Now, if the content changes in only the main page but the 3 tiles are >static in nature, wouldn't the resultant HTML document rendered on the >server be different and therefore the content of the tiles wouldn't be >cached? > Again right. > >I can understand if perhaps the tiles are cached ON THE SERVER. This >makes sense to me. But, on the client?? Was I told something wrong (what >I suspect) or is there something here for me to learn? Thanks all! > I think that with "caching" they meant something else, but I am not able to read their thoughts at the moment :-P Or maybe, they again confuse Tiles with Frames... They must be the brothers of those who don't understand that calling a frameset and its frames means making several http requests... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
