With reference to having multiple instances of the NewsFeeds module on the same page...

Yes, we tried this also and found that if more than one feed expired and requires an update then only one instance gets refreshed. The result to the page visitor is less than desirable. The visitor will need to hit the browser refresh for each instance on the page!

Ideally, from a users point of view I would like the module to:

• Not delete the cached feed until a new copy is retrieved - it does not even have to be refreshed on the page that invoked the refresh (just on the next view)
• Perhaps the caching can be a scheduled task rather that the performance hit that occurs to the visitor currently?

Currently, if the feed is updating the visitor can not even move away from the page until the refresh either completes or timeouts.

IMHO version 4.0.0 should not have been deployed with DNN 4.9.0 due to the current development of the module when compared to the previous version.

In our case the use of the NewsFeeds module is low priority but we are keen to see it's progress as it introduces some very valuable architecture and functionality, for now we will continue to leave it on our test machine and maybe single instance applications.

Cheers

Craig