I was looking for a way that content on a view would be automatically refreshed (without user interaction) then a new content is added to the database. Somebody showed me this views hack and it would probably do what I want. But because I would need to set a really short period it would cause a website to use considerably more recluses.

So I was thinking maybe not the whole view has be updated. Considering the fact that I do not have to change overall display just add data which was added to the database. Maybe there is way just to add just needed content. Something like partial refresh.

I continued my search and found an interesting library called Pubsubhubbub it uses PusH technology and adds data to a display only then it is added to database. There is already a views rss sub module called views rss pubsubhubbub module which uses this technology with views but it is just for rss feeds. Could it be possible to replace or call (more likely scenario) AJAX reload using this technology? In my case I am adding most of the data from other RSS feeds using Feeds module and it`s native pubsubhubbub integration, so calling a view refresh then a pubsubhubbub is active would be very smart. It would save a lot of resources add would be a really nice addition to Views features set.

Problem is that I do not know how to accomplish this, so I am looking for some tips or opinions Iif you think there is a better way of doing it I would happy if you would share.

Comments

dawehner’s picture

dawehner
Primary language German
commented
Category: feature » support

Well maybe you could extend the module which is part of views_hacks with pubsubhub support, i'm not sure how we should help here.

There are some folks using node.js together with drupal and views, which allows you to push stuff out there directly, which might be helpful for you as well.

POVYLAZZZ’s picture

POVYLAZZZ commented

I have heard about node.js but have not checked it out yet. Thanks for a clue I will try to analyze it and maybe use it.

kars-t’s picture

kars-t commented
Status: Active » Closed (won't fix)

Dear fellow Drupal enthusiasts,

This issue is now lasting for a very long time in the issue queue and was unfortunately never solved. As Drupal is a open source project, everyone is helping on a voluntary basis. That this was not solved is nothing personal and means no harm. But perhaps no one had time to deal with this issue, maybe it is too complex, or the problem was not described comprehensibly.

But this issue is not the only one. There are thousands of issues on Drupal.org that have never been worked on or could not be processed. This means that we are building a wave that is unmanageable and it is a problem for the Drupal project as a whole. Please help us keep the issue queue smaller and more manageable.

Please read again, "Making an issue report" and see if you can improve the issue. Test the problem with the current Core and modules. Maybe the problem doesn't exist anymore, is a duplicate or has even been solved within this issue but never closed.

Help can also be found for it on IRC and in the user groups.

In order to close this issue, I have set this issue to "Closed (won't fix)".

If there is new information, please re-open the issue by changing the status to active.

--
This issue was edited with the help of Issue Helper