sikkor

I think I tried most of the RSS readers for the Pocket PC platform so far. By most I mean: Egress, Pocket RSS, pRSS, FeederReader, and few others. Most of them seem to have one common tendency that really bugs me. After I read the feed and go to the next one, the previous is not released from the memory. So let's say that after I read like 5 cached feeds, RAM is clogged completly.

All of these applications were installed on the SD card, one at a time. Is that a mistake for RSS apps? Oh, and BTW, if the application allowed to store the cache file on the SD card, it was stored there.

MobileSmith

Originally Posted by sikkor

I think I tried most of the RSS readers for the Pocket PC platform so far. By most I mean: Egress, Pocket RSS, pRSS, FeederReader, and few others. Most of them seem to have one common tendency that really bugs me. After I read the feed and go to the next one, the previous is not released from the memory. So let's say that after I read like 5 cached feeds, RAM is clogged completly. All of these applications were installed on the SD card, one at a time. Is that a mistake for RSS apps? Oh, and BTW, if the application allowed to store the cache file on the SD card, it was stored there.

With FeederReader, the feed data is stored (by default) on the same Storage Card as the application, or you can specify a different folder in the Options. FeederReader is optimized as much as possible for operation this way. RAM is certainly the fastest, but is usually not the most available ;-) I started out using a Secure Digital card that was REALLY SLOW and now recommend SD cards faster than 30x. They seem to work great! I currently use a Compact Flash for storing feeds and podcasts and videocasts.

Regarding the delete after Read, you can specify to EXPIRE READ items differently from UNREAD items. And you can set this really low (maybe 0 minutes, but I haven't specifically tested that!) so that message that you have read are automatically EXPIREd very quickly. At any time, you can select "Manual Expire" which will find and either delete or schedule to delete all aged messages. Or you can set a message to EXPIRE automatically, which means that on the next Update all messages that are Read and past the EXPIRE age, will be scheduled for deletion. FeederReader will delete the message completely when the message is ELAPSED from (i.e. no longer appear in) the original feed. This means that you are right, the memory for the message is freed only after the message no longer appears in the original feed AND it is EXPIRED. This is to prevent FeederReader from reading the message again from the feed, and seeing it as a new message.

I originally conceived FeederReader to get rid of the memory for messages that are Expired entirely under the control of the user, and FeederReader is still designed to add this functionality, if enough people request it. But yours is the first message I've seen requesting that functionality, so it has never been on my priority list.

I take functionality requests from users on the FeederReader Forums. I just went through the list this weekend to organize and prioritize them. The best way to request functionality within FeederReader is to post a message to the forum dedicated for that purpose!

I hope this helps you understand the design philosophy of FeederReader and I hope you continue to use FeederReader!

Greg Smith
Author, FeederReader - Pocket PC *direct* RSS text, audio, video, podcasts
www.FeederReader.com - Download on the Road