SSI-like feature in ASP.NET / ASP.NET MVC -
This could be a heterogeneous question, we have a large site where many pages are still in ASP, mostly dynamic Not included, but they are included through SSI or server. It can look like a poor person's caching, but it's working really well and I think Microsoft has optimized IIS quite a bit for this scenario.
Now, we want to achieve something like this: ASP.NET / ASP.NET MVC. We will generate HTML snippets from time to time (usually per hour or more) which we will call ASP.NET The main site Chrome, which want to include in ASP.NET MVC Rappers, provides some navigation, and possibly some other dynamic content related to the snippet. So this is a mix, but the point is that the generated HTML is generated from time to time due to external reasons, primarily for reasons of performance and keeping our server farm in sync.
I was able to find the closest thing in ASP.NET:
<% Response.WriteFile ("GeneratedSnippet.inc"); & Gt%;
Which
& lt;% Server.Execute "GeneratedSnippet.inc"% & gt; Seems to be equal. In ASP
This is probably faster because there is no code to execute. But this is probably not as equally efficient as:
& lt ;! - # include file = "GeneratedSnippet.inc" - & gt; As I mentioned above, I suspect that IIS has been adapted to handle SSI and is also included in ASP years. On the other hand, the possibility of Response.WriteFile actually reads the file and spits it out, can anyone have any insights into two or some experiences? Maybe I worry too much, but most of our heavy traffic content still runs on ASP and uses lots of SSI, and so there is a slight difference in the response. WriteFile can be deposited and may have a visual effect.
What questions do you have? :)
SSI is dead Yes, it was more optimized than server, but it is not effective for cash control not only in server but also in browser.
If you use a lot of SSI, then the server must check all the revised status of related files for each request you can not control the HTTP header for example, end of example And etg.
There are several ways to control and invalidate cache in ASP.NET and ASP.NET MVC (which can also perform better, better code in more scalable design and maintenance.)
Comments
Post a Comment