[geeklog-devel] Dynamic Feeds with access control for Soc

[jamil haider]

Hi,

 I after some time toiling with the source code I think that Apparently there are two parts of the project: first is the dynamic feeds and the second one is the access control. Access control doesn't seem to be a big deal (May be it is beause I dont have much knowledge of the securtiy architecture of the GL:). As for the dynamism of feeds I was thinking on the lines as event handling is done in Java where we register our method to some action listener and whenever some event is generated we get to know. This is similar to the polling vs interrupt scenario. Currently geeklog has polling and we can replace it with some interrupt based system. We can have our main interface with 
some general methods. We can then implement them in our adapter classes. Whenever a user want to get some feed, some method will be called that register the relevant strings/url with some event listener. This architecture will hopefully reduce the server load as there would be less queries to our database and we wont be need to call the COM_rdfUpToDateCheck after regular intervals. As for the access control, it would be really great if you could provide me some pointers. Please reply soon as it seems that I am a behind the schedule.

Regards 
Jamil Haider

> Today's Topics:
> 
>    1. Dynamic Feeds for Soc (jamil haider)
>    2. Re: Dynamic Feeds for Soc (Dirk Haun)
>    3. Re: Hello and introduction (Dirk Haun)
>    4. SocNet (hitendra chauhan)
>    5. Introduction - (Google SoC more Spam-X modules) (Sumesh KS)
>    6. Re: GSOC - Socnet (Jakh Daven)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Fri, 19 Mar 2010 23:03:42 +0500
> From: jamil haider <jamil_fawad at hotmail.com>
> Subject: [geeklog-devel] Dynamic Feeds for Soc
> To: <geeklog-devel at lists.geeklog.net>
> Message-ID: <BAY127-W3198935485C707B2D8F85862A0 at phx.gbl>
> Content-Type: text/plain; charset="iso-8859-1"
> 
> 
> Hi,
> 
> I am Jamil Haider doing computer engineering from Pakistan. I was interested in adding support for dynamic feeds with access control. On the ides page it was written that there will be need for simplification of Plugin API for feeds. Any pointers pertaining to that required simplification are welcome. I am also bit confused about the scope of the project because it seems that to implement this feature I will have to poke into many different areas. Any help will be greatly appreciated.
> 
> Regards
> Jamil Haider
>  		 	   		  
> _________________________________________________________________
> Your E-mail and More On-the-Go. Get Windows Live Hotmail Free.
> https://signup.live.com/signup.aspx?id=60969
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://eight.pairlist.net/pipermail/geeklog-devel/attachments/20100319/7fc697b0/attachment-0001.htm>
> 
> ------------------------------
> 
> Message: 2
> Date: Fri, 19 Mar 2010 20:30:04 +0100
> From: "Dirk Haun" <dirk at haun-online.de>
> Subject: Re: [geeklog-devel] Dynamic Feeds for Soc
> To: geeklog-devel <geeklog-devel at lists.geeklog.net>
> Message-ID: <20100319193004.945262577 at smtp.haun-online.de>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> jamil haider wrote:
> 
> 
> >I am Jamil Haider doing computer engineering from Pakistan. I was
> >interested in adding support for dynamic feeds with access control. On
> >the ides page it was written that there will be need for simplification
> >of Plugin API for feeds. Any pointers pertaining to that required
> >simplification are welcome.
> 
> Well, currently plugins have to duplicate a lot of code when they
> provide a feed. The question here was whether this code duplication
> could be avoided.
> 
> Maybe I'll better start with the second part of your question:
> 
> >I am also bit confused about the scope of
> >the project because it seems that to implement this feature I will have
> >to poke into many different areas.
> 
> Generally speaking, the code that actually creates the feed in the
> various formats is in system/classes/syndication. Above that is system/
> lib-syndication.php, which is either called through the Plugin API or in
> some cases directly (for article feeds).
> 
> I'd suggest you have a look at what happens when you save a new story -
> follow the calls through COM_rdfUpToDateCheck down to writing the feed
> file. Then do the same for a plugin that supports feeds, e.g. the
> Calendar plugin.
> 
> When you follow both paths, you'll see the duplicated code I mentioned
> above. If you see a chance to reduce or eliminate that code duplication,
> that would be welcome. But that's only the bonus part of this project.
> 
> Yes, this project would potentially touch on many different areas of the
> code. Currently, when a new item is saved or an item is updated,
> COM_rdfUpToDateCheck is called and all feeds the that are affected are
> updated.
> 
> Dynamic feeds will have to work the other way around: A request for a
> feed comes in and the items in it need to be collected and delivered.
> 
> For some sort of feeds, there may be a middle ground: The stories for a
> feed (or rather, their story id), for example, could be cached in the
> database. But this won't work for a feed for searches.
> 
> Part of the research for this project should be to figure out how far we
> could go (technically and realistically, given the constraints of the
> Summer). In some systems, you can turn pretty much every URL into an RSS
> feed by attaching some parameter to it. Something like that is pretty
> cool but probably not realistic for Geeklog. But some of the more
> dynamic examples listed on the ideas page (feed for moderation, feeds
> for search) seem to be within reach and would be very useful.
> 
> Hope that helps :)
> 
> bye, Dirk
 		 	   		  
_________________________________________________________________
Hotmail: Trusted email with Microsoft’s powerful SPAM protection.
https://signup.live.com/signup.aspx?id=60969
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist8.pair.net/pipermail/geeklog-devel/attachments/20100330/9dc151e0/attachment.html>