Last post Dec 01, 2005 07:21 AM by EmperorWal
Nov 28, 2005 08:33 AM|CurlyFro|LINK
Nov 28, 2005 09:52 AM|nokiko|LINK
Nov 28, 2005 10:25 AM|CurlyFro|LINK
Nov 28, 2005 12:11 PM|sowens|LINK
Nov 28, 2005 12:31 PM|rodneyjoyce|LINK
Nov 28, 2005 02:07 PM|liorlustig|LINK
Nov 28, 2005 02:08 PM|ikamiksok|LINK
Nov 28, 2005 08:57 PM|CurlyFro|LINK
Nov 29, 2005 12:41 AM|lou|LINK
My pref would be personal portals and I say that from a admin standpoint. There is nothing wrong with what you did that I can think of. .
Nov 29, 2005 08:44 AM|rodneyjoyce|LINK
Nov 29, 2005 08:39 PM|CurlyFro|LINK
Nov 30, 2005 04:16 AM|rodneyjoyce|LINK
Nov 30, 2005 04:07 PM|EmperorWal|LINK
For what it is worth, I took an approach similar to what Jason did with
www.yapclub.com (ikamiksok). I built an extension framework for DNN and then I take standard modules and modify them to play in my framework. I also need
to provide a rich community site, so separate portals for each user is not an option.
If you look at modules like the blog or forum modules you'll see that they already provide a mechanism for users to post and manage their own content. A forum can support thousands of users, but it only requires one page in the portal.
The Forum approach does not run into the scalability limitations of having too many pages cached or too many roles to manage. The module is responsible for determining if a user can edit content.
For my site I just generalized that approach and now I'm modifying modules to work in my framework.
I never came up with a good way to build a highly scalable solution that would let individual users own their own content and use standard DNN modules with standard DNN edit mechanisms. I had some ideas, but in the end modifying the modules
I needed to use seemed the most practical approach. Rodney's approach has an advantage that any DNN module will play in his portal. The approach I've implemented for my own site allows standard DNN modules to be used for general site content, but custom modules
are needed if you want to provide user owned content.
Nov 30, 2005 06:57 PM|lou|LINK
The problem is this would be over 2000 portals which is far too hard to manage with the current tool set, especially when 99% of the students need to upgrade to a new year every year.
The problem would be 2000 subirectories.
Nov 30, 2005 10:15 PM|CurlyFro|LINK
Dec 01, 2005 07:21 AM|EmperorWal|LINK
When I first started down the path of building a community site with user owned content I looked into the one tab/one role for each user model. From the thread
http://forums.asp.net/1024204/ShowPost.aspx you can see why I didn't go down that path (have I really been working on this since August?).
One test to see if the number of pages is causing you performance problems is to look at the .NET CLR Memory: % Time in GC performance counter. If 500 TabInfo objects are created on every request, I expect you'll see tons of Garbage Collector activity just
trying to keep up with the allocation and clean up of all those objects in memory. The article
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/highperfmanagedapps.asp may be helpful.