Sitemesh or XSLT for layout

Hi to all,

I am designing a layout for my crm project now.

Now i am ended with 2 options one is sitemesh to define the layout or XSLT to define a layout.

Sitemesh will run at runtime from the server , it wont cause any issue if the number of request is high?

I guess XSLT will run at the browser based on the Xpath , is this correct?

Which one is better to use?

Please help me

Thanks

In a SiteMesh vs. XSLT you can always say who is the best. For you, I think SiteMesh would be easier to use, but the page is rendered on the server, and as you said, for a big number of requests it might cause you trouble. How the application will be deployed? Is widely used? Or just internally in a company for example?

Daniel Doboseru wrote:In a SiteMesh vs. XSLT you can always say who is the best. For you, I think SiteMesh would be easier to use, but the page is rendered on the server, and as you said, for a big number of requests it might cause you trouble. How the application will be deployed? Is widely used? Or just internally in a company for example?

SiteMesh is nice if you are producing more or less "static" pages depending on some input and/or time. Then you can always use a web cache or even an accelerator such as Akamai or EdgeCast to deliver your pages.

However, if your pages contains a lot of data that are of a more personal kind, such as account information, user statistics and such, I often choose to have a more or less "static" page loaded from the server that contains placeholders for the personalized data and then we load that data using web service. Often we return a JSON-object from the server and "loads" it into the page using scripts.

Thank-you for all your replies

Dilip