Dear Ramadi, I would recommend using SiteMesh (it's a filter) while you continue using Struts & Tiles.
If you have any exceptionally large pages you wish to display (i.e. pages and pages and pages of content) you might want to watch out for String buffer issues. Why? SiteMesh receives a complete page before quickly parsing it and wrapping it per it's configuration. The result is that TRULY large pages might blow a string buffer limit. In practical use that may never happen but if you have a heavy amount of tables and/or long pages, the string buffer size might become an issue. Do I know what that size limit might be? No. I just read about it while researching and testing out SiteMesh a few months ago and thought I'd provide a warning, just in case. After all, you never know how much people will write. Regards, David -----Original Message----- From: Ramadi Pearse [mailto:[EMAIL PROTECTED] Sent: Thursday, June 16, 2005 5:30 PM To: user@struts.apache.org Subject: Best Practices for static content Does anyone have best practices on how to compose or decorate stand-alone static content? It seems overkill to have to modify tile-defs.xml for each new static page I want to add to the website. Is SSI or SiteMesh more appropriate here? By the way, this is to complement a web app which already uses Tiles to compose the data portion of the app. Thanks! __________________________________ Discover Yahoo! Have fun online with music videos, cool games, IM and more. Check it out! http://discover.yahoo.com/online.html --------------------------------------------------------------------- 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]
