Does anybody know (and be willing to explain) how an RSS portlet is supposed to decide that it's shown the same page long enough and show a new one? It seems to involve how long an entry is stuck in the JetspeedDiskCache (looks like that should be 15 minutes only) and how often the source actually changes - but the portlet itself seems to cache the results and this needs to be updated... Since it's a FileWatcherPortlet it seems to want to change when the disk changes, but won't the disk remain the same until somebody asks for a new version?
If anybody has a brief explaination that they would share I'd appreciate it. In my tests, a very old version of the RSS content that starts up in the cache directory and should have expired at best after 15 minutes is never expiring for the latest version of the feed... I'm trying to figure out why. Thanks! - Glenn --------------------------------------------------------------------- Glenn R. Golden Systems Research Programmer School of Information University of Michigan [EMAIL PROTECTED] 734-615-1419 --------------------------------------------------------------------- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
