I haven't found any solution yet! :( Can someone please help in making a real-time aggregator? Please?
On Sat, Apr 17, 2010 at 11:33 PM, vimal atreya <[email protected]> wrote: > Alex, > > I guess "Feeds" just create new nodes of the imported feeds. Isn't it? > > > > On Sat, Apr 17, 2010 at 11:49 AM, Alex Barth <[email protected]> wrote: > >> Hi matthew, >> >> I maintain an aggregator for drupal. (Feeds). I use a drupal-independent >> library for all the pshb related lifting: >> >> http://github.com/lxbarth/PuSHSubscriber >> >> On Apr 16, 2010, at 12:18 PM, Matthew Terenzio <[email protected]> >> wrote: >> >> Pádraic, That's neat. I hadn't seen the ZFPlanet thing before. >> >> Regarding the Wordpress plugin. If you refer to Joseph Scott's plugin I >> believe it acts as a publisher or a hub. I haven't seen anything that acts >> like a client in Wordpress yet, which would probably be what you need to >> make an aggregator. >> >> I'm working on that now in case someone knows of something I missed. I >> hate to waste/duplicate effort. ; ) >> >> >> On Fri, Apr 16, 2010 at 3:08 PM, Pádraic Brady <<[email protected]> >> [email protected]> wrote: >> >>> Hi Vimal, >>> >>> The question depends on a lot of factors, so I'll stick to broad design >>> approaches and offer an example in PHP you can examine in detail. >>> >>> The main thing is that any current aggregator has to deal with both PuSH >>> enabled and non-PuSH enabled feeds. So you're really building two distinct >>> systems. Obviously building in twice the complexity isn't a great idea so a >>> good approach is to keep the following separate: >>> >>> 1. Polling of feeds. >>> 2. Processing of feeds. >>> 3. Handling of processed entries. >>> >>> This is the core of any aggregator but the separations are important once >>> you bring in PuSH. Adding PuSH includes adding: >>> >>> 4. PuSH processing (callbacks, subscriptions, unsubscriptions) >>> >>> But with the first three, you can reuse 2 and 3 for all incoming PuSH >>> notifications. It's a common aggregator mistake to merge the polling >>> (fetching) with the processing making them hard to separate and reuse for >>> PuSH. >>> >>> Onto the example, I created a demo application for PuSH (a simple >>> aggregator) for the Zend Framework (PHP). In the application, all processing >>> is performed within a Model (this takes over from the moment a feed is >>> either polled or received via PuSH notification callbacks). You can find the >>> source code at: >>> >>> <http://github.com/padraic/ZFPlanet>http://github.com/padraic/ZFPlanet >>> >>> Please feel free to ask any questions on how it operates on or off list. >>> It gives a broad example of the database schema, the use of >>> Zend_Feed_Pubsubhubbub (if your question is related to PuSH implementation >>> itself you can look there also - <http://framework.zend.com> >>> http://framework.zend.com), and some simple scripts for use with cron to >>> schedule polling. You should also note that Wordpress and Drupal both have >>> PuSH plugins/modules you may want to research depending on how/if your >>> aggregator is being built on either of these platforms. >>> >>> Paddy >>> >>> Pádraic Brady >>> >>> <http://blog.astrumfutura.com>http://blog.astrumfutura.com >>> <http://www.survivethedeepend.com>http://www.survivethedeepend.com >>> OpenID Europe Foundation Irish Representative<http://www.openideurope.eu/> >>> >>> >>> ------------------------------ >>> *From:* vimal < <[email protected]>[email protected]> >>> *To:* Pubsubhubbub < <[email protected]> >>> [email protected]> >>> *Sent:* Fri, April 16, 2010 7:17:59 PM >>> *Subject:* [pubsubhubbub] Aggregator with Pubsubhubbub? >>> >>> Hey guys, I was wondering how to make an aggreagtor with PuSH. I >>> couldn't figure out how to start with it. I just developed websites >>> with drupal and wordpress before. Can you please explain me the basics >>> to start with an aggregator with PuSH? Please? >>> >>> >>> -- >>> Subscription settings: >>> <http://groups.google.com/group/pubsubhubbub/subscribe?hl=en> >>> http://groups.google.com/group/pubsubhubbub/subscribe?hl=en >>> >> >> >
