|
|||||||||
|
|||||||||
|
|||||||||
| |
|||
 |
|
|
|
|
|||||||||
|
|||||||||
|
|||||||||
| |
|||
|
|
|
|
| |||||||||
 |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Display Modes |
Dev Articles Community Forums Sponsor:
|
|
|
|
#1
August 28th, 2003, 02:35 AM
|
|||
|
|||
|
Server.Execute
When I'm developing a website I'm using a lot of includes to save me from some work, but not everything can be included. This means that I will need to make several pages with the same design.
To save me some work, is it a good idea to use Server.Execute to call different pages into my default.asp page design using If then / Case Else variables? Or will this put to much stress on the server and will search-engines have more trouble in finding the pages?
|
|
#2
August 28th, 2003, 04:03 AM
|
||||
|
||||
|
#INCLUDE and server.execute are essentially the same thing, but with .execute, you can conditionally call a file using an If/Then for example.
The best way to see which is best for you is to actually do some tests, and see which performs better. There's quite a few articles on the pro/cons of each if you have a look around on google. This article gives you a brief run-down on each. This 4guysfromrolla.com article is informative also.
|
|
| Viewing: Dev Articles Community Forums > Programming > ASP Development > Server.Execute |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
 |
|
|
Del.icio.us
Digg
Google
Spurl
Blink
Furl
Simpy
Y! MyWeb
Linear Mode
