Thank you Mariette for your constructive opinion.  It appears that today constructive criticism isn't wanted...

Crispy,  I've been a developer a long time now and you'll have to excuse me if I can't see your view that just because it's not easy to do, it's not a good idea.  I think if you will "think before you speak" you will understand that is very possible to achieve what I have requested.  Have you ever used WebSphere or Windows Explorer?  I understand that if your caching isn't capable of determining who is logged in and caches correctly then the caching is lacking and perhaps there should just be an option to disable it if I would rather have full-featured search and aggregation.  In fact, I (as are most others out there it seems) have disabled DNN caching for most of my modules anyway because it is just too buggy and dangerous to use.  I recently lost an entire site because of it...

It was not my intention to start a flame war, but rather to get some insight as to why things work the way they do.

Ian

Ian,

All you had to do is ask why it was that way instead of 'took the easy way out'. I admit I responded very aggrevated about the way you said that and probably should have waited the normal amount of time I wait to respond to something that frustrates me. I can explain several reasons why and if you read the thread I have already offered some insight as to why this was done this way so far.

Mariette, you read my response and don't like my tone. That is your opinion,  but how is me voicing my frustration any different than you posting "I don't like the tone of this thread at all".

I have a hard time understanding how the "aggregated" option could be considered a bug based on the fact that it does not include private forum threads. The forum exposed under the Aggregated heading is very clear that only "Public" information will be displayed:

All Public Forums
An aggregated view of all public forum threads.

I suppose it is possible that users of the software do not read the text displayed by the application, and then are confused by the results. But does Chris really deserve the criticism?

I implemented the Aggregated forum feature and documented my throughts behind it in this blog post. As much as any of you, I really wanted to include private forums as part of the implementation - since there are many private forums on dotnetnuke.com which I need to constantly monitor. However, I discovered during implementation that there was a serious tradeoff to consider. In order to support private forums in the aggregated view, the application would need to suffer a serious performance impact. Since this affects scalability and customer satisfaction and I concluded that a win/win compromise could be obtained by only supporting public forums in the aggregated view ( resulting in only a minimal impact on performance ). Text was added to the forum application to try and make it clear that only Public forums are supported.