Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsNews FeedsNews FeedsNewsFeed & Local Modules fail to workNewsFeed & Local Modules fail to work
Previous
 
Next
New Post
3/26/2009 10:13 AM
 

Hi guys,

I'm not sure about the outcome of this thread, frankly. The issue is authentication of the current thread. But this means you should no longer do any caching. I've taken this module down the path of caching and aggregation to distinguish it from the XML/XSL module. With caching we no longer take the current thread/user into account. It could be another user in 10 seconds time that we want to show the cached feed. Instead we offer the ability to supply user credentials explicitly for feeds. Do you see where this is heading? The next version is going to do background loading of feeds. This will further improve performance. It means that in due course we might even deprecate the dependence on Ajax for rendering. As you can understand, background loading means you have no current user any longer. The module is thus drifting further away from your use case. I'd say that either you use the authentication explicitly or you use an XML/XSL module for this.

What are your thoughts?

Peter


Peter Donker
Bring2mind http://www.bring2mind.net
Home of the Document Exchange,
the professional document management solution for DNN
 
New Post
3/26/2009 10:57 AM
 

Peter,

Not sure I completely understand why the module cannot use credentials to decide whether to show a module instance or not.  It seems like that's the first test to do, then, make a choice about rendering a feed.  I've always felt that using memory cache was preferable to reading from a database, but that's not always a workable model for a newsfeed, in my opinion.  If a feed is fetched from the source URL, when setup, there is an opportunity to capture the relevant data and write it to a database table, which would include a TTL, either from the source, or calculated at the fetch time.  Any subsequent attempt to access that information could be subject to authentication by the module permissions, and render if authenticated.

The background loading mechanism would be responsible for deciding whether to fetch an update using  the TTL period, skip days, skip hours of the feed.  If fetched again, the feed information is written to the database, and available to the next user.  I know that some balk at using trips to a database to render a newsfeed, but I think it's better to fetch from a database, than to fetch from a newsfeed source which could possibly fail due to many reasons.  Such failures could be trapped and the previous information is preserved, giving the user something to see, rather than give them nothing.  Ajax could still be used to render the feed from a trip to the database.  Yes, more trips to the database to read, but it beats the heck out of using Ajax to read from the source URL performance wise.

The problem with background loading is needing to time it.  The scheduler only works when a user accesses the site, and fires off the checks.  At least, that's what I've seen in my attempts to fetch news using it.  So, that's another topic or facet to discuss.

Just a few thoughts, and I admit, I may be missing your point entirely, so we can continue to discuss the issues.  I know many folks are interested in your thoughts, and appreciate the opportunity to shape the direction of the module.  You know it's one of my favorite subjects. 

 
New Post
4/3/2009 10:02 AM
 

Hi Peter,

Can you confirm that using supplied credentials, the newsFeed module should be able to grab the RSS XML from another module like the announcement module. As this is currently not working for me.
It looks to me that the supplied credentials are used for logging on to a remote website.

I must admit that we have Dotnetnuke running with a custom authentication module to support SSO and this might complicate thing a litte bit.

Kind regards,

Jos

 

 
New Post
8/14/2009 7:55 AM
 

Were you ever able to address this?  I'm having the same problem and after 14 hours of binging, googling and searching here, I still cant find a fix.  If this problem so rare I hope that means it's an easy fix.

I was having this problem both in the production server and on my local machine.  Setting "integrated network authentication" and anonymous access fixed it on my local (XP) development environment and my rss readers and read syndication from modules local to them, but the same change didn't work on the server (IIS 6.0).

I don't think this is the news module's fault but any help would be appreciated.  Syndication is such a powerful feature and I'd hate to not be able to use it.

Thanks in adavance,

Lloyd

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsNews FeedsNews FeedsNewsFeed & Local Modules fail to workNewsFeed & Local Modules fail to work


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out