Currently the Lars Blogger RSS Subscriptions provide a problem in the way that for each subscription a new directory is added to the /home/pi/openacs/rss/pinds_blog_entries directory. This file is needed so users can access the site and get their rss subscription. With 32*** subscriptions you suddenly hit the linux limit for the number of directories in one level.
This design was chosen so we would not run into problems with a multitude of RSS Readers hitting the database to get the XML Feed. In my opinion though this is *highly* unlikely to happen.
Therefore I'd say it is a design flaw to store the file in the file system as you could just as well store it in the database and use cr_write_content or similar to deliver the "file" back. As the impl_name is provided as well as the summary_context_id we can figure out the impl_id from the impl_name (acs_sc_impls) and store the XML as a new field in rss_gen_subscrs.
This would mean rewriting the rss-support package so that rss_gen_report will store the XML in the database and rss_gen_report_file will deliver the XML instead of the filename. Which means rewriting all packages that use rss_gen_report_file.
The alternative solution would be to adopt the system used in content-repository to store the files, so you have a multitude of directories and subdirectories aso.
Please advise, as we are going to have to fix this for a client of ours and either way probably is an equal amount of work, but I'd prefer the database solution.