Forum OpenACS Development: Re: RSS Design Problem

Collapse
2: Re: RSS Design Problem (response to 1)
Posted by Dave Bauer on 10/02/06 02:39 PM
Malte,

Obviosuly you are not building a popular public web site, but must be using RSS for some other type of system.

"caching" the rss in the database seems like a reasonable compromise, but it probably should be optional. It only requires one hit to the database to deliver the file instead of actually rebuilding the content.

Probably the "ultimate" solution is to use the syndication table to cache the xml fragments, and rebuild the RSS from there. I am using that for all the RSS support I am builiding for clients these days. It allows for custom RSS feeds bsaed on various criteria including search.

Collapse
3: Re: RSS Design Problem (response to 2)
Posted by Malte Sussdorff on 10/02/06 06:24 PM
Okay, maybe I'm not clear. The current design of OpenACS stores the RSS in the file system with each impl_id / summary_context_id using one directory which contains exactly one rss.xml. This is the reason why the popular public web site brings me so much trouble.

So, instead of "caching" the rss.xml in the filesystem I wanted to cache it in the rss_gen_subscrs table, as this is the table which is used for generating the rss feed anyway.

Not sure though what you are talking about with the rebuilding the RSS from the XML fragments. Maybe you could elaborate a little bit more?

To be honest, I have not much clue about RSS at this point in time. I just need a solution for the simple problem that I ran out of directories on a public server of a client using Lars Blogger.