Author |
Topic  |
|
snaayk
Senior Member
   
USA
1061 Posts |
Posted - 06 November 2003 : 12:44:01
|
I have really started getting dirty with .NET now. As I see the different methods that some folks use I was wondering what your thoughts were on the use of dynamic loading of user controls.
One could, for example, create one page (Default.aspx) and just load the content based on the querystring/post result. This would allow one to create a "frame" for the page and plugin what is needed. I have this now, I load the main part of a page depending the querystring and load different left/right side navigations depending on the path (where you currently are in the site).
Pros and cons to this? I was wondering if only serving one page for an entire site would not be very efficient. If every request had to access this one page, all the time, would it be bad for performance - then again, that's what is done with includes. Although this method currently forces me to create a lot of case statements, I am working on a straign load from the variable (if the file is found in the directory) allowing for an even easier method to add additional "pages" to the site.
Your thoughts or methods?
|
|
DavidRhodes
Senior Member
   
United Kingdom
1222 Posts |
Posted - 06 November 2003 : 16:14:29
|
Nathan's ASP.NET Forum uses that method, haven't tried it myself |
The UK MkIVs Forum |
 |
|
Nathan
Help Moderator
    
USA
7664 Posts |
|
Jeepaholic
Average Member
  
USA
697 Posts |
Posted - 07 November 2003 : 02:23:22
|
It's a good way to program. Pages are pages. If a bunch of people are hitting one page vs. a bunch of different pages, it's still a hit on the processor. I'm in the middle of developing an application that has massive customization abilities in this regard...various modules in various locations based on various inputs.
The beauty of DotNet is that it allows for some really cool cacheing features, as needed, to speed things up. |
Al Bsharah Aholics.com
Jeepaholics Anonymous Broncoholics Anonymous Network Insight
|
 |
|
Nathan
Help Moderator
    
USA
7664 Posts |
Posted - 07 November 2003 : 15:10:06
|
Actually, it should help. Because ASP.NET can cash one page, but if you have 45 pages that take more resources.
The code should all be in DLLs anyway. |
Nathan Bales CoreBoard | Active Users Download |
 |
|
Nathan
Help Moderator
    
USA
7664 Posts |
Posted - 08 November 2003 : 03:48:36
|
Oh, and just an interesting point.
Microsoft will be officially adding this to ASP.NET 2.0 whith the introduction of master pages. (You may have noticed some microsoft sites are now using this technology and have files with the name filename.mspx) |
Nathan Bales CoreBoard | Active Users Download |
 |
|
|
Topic  |
|