服务器端包含与ASP.NET技术是有性能差异? [英] Server Side Includes vs. ASP.NET Techniques is there a performance difference?

查看:115
本文介绍了服务器端包含与ASP.NET技术是有性能差异?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我最近聘请来更新ASP.NET 1.0的网站,母版页之前创建可用。因此,网页上有服务器端包含(SSI),如&LT; - #包括文件=footer.html - &GT; <!/ code>。我正要更新包含标记previously在SSI的母版页的* .aspx页。我相信这是做的,特别是从维护的角度正确的事情。然而,一个同事坚信表现会遭受所谓SSI的是一个非常轻量级的方法(他的话不是我)。我找不到关于一种技术与其他的性能的信息。如果有,我相信母版页和Web控件的等优势仍然是比较重要的。您的想法?

I was recently hired to update an ASP.NET 1.0 site, created before master pages were available. Hence the pages have server side includes (ssi) like <!-- #include file="footer.html" -->. I was about to update the *.aspx pages with a master page that contained the markup previously in the ssi's. I'm convinced this is the right thing to do, especially from a maintainability perspective. However a co-worker firmly believes performance would suffer as supposedly ssi's are a very 'lightweight' technique (his words not mine). I can't find much information regarding performance of one technique versus the other. And if there is, I believe the other advantages of master pages and web controls would still be more important. Your thoughts?

推荐答案

在一个小的静态页面的情况下,我不知道,它可能pretty接近的性能,明智的。你可以运行一个负载测试得到一些实实在在的数字,并找出。

In the case of a small static page, I don't know, it's probably pretty close performance-wise. You could run a load test to get some hard numbers and find out.

不过,真的没有的劣势的使用母版页,并有一大堆的优点的就设计和管理去了。

However, there's really no disadvantage to using a master page, and there are a whole lot of advantages as far as design and management go.

这篇关于服务器端包含与ASP.NET技术是有性能差异?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆