|
Undocumented WriteBlock Code Sample - 2eNetWorX
|
|||
| 2eNetWorX :: ASP, VB, Asp.Net, Vb.Net, C#, dotNet, .Net OpenSource Projects |
| MyDev | What's New | Projects | Tutorials & Articles | Services | Stats | Contact Us |
| Guest-16993 | /dev :: home :: samples :: performance | 596 online visitors |
» Contributions
» Recordset Cache » OpenSource » Statisticus » OpenCYA!
» Undocumented... » Ask For Login » DSN'less Connection » Who's Online? » (All Samples)
|
Code Samples :: Undocumented WriteBlock Feature
There are various articles about performace saying that
you should keep the number of switches between asp and
html blocks at minimum. I agree.
Response.WriteBlock(BlockNumber)
The following example is a mixture of asp and html
blocks. When this page is first requested, it is
compiled and cached.
test.asp
<html>
Keep in mind that number of WriteBlock's effect the performace
of your asp page. The higher the number of html blocks you have,
the higher the number of WriteBlock calls the ASP engine should
execute.
I hope this sample gives you a quick overview of
the pre-compilation and WriteBlock function.
by Hakan Eskici |
Bot: Msn
echoPANEL, Free .NET
FogBugz Hosting Plans
|
| privacy policy , license , disclaimer , © 2000-2004, 2eNetWorX. [page generated in 516 ms.] |