> I'm not sure if this action of basically skipping the caching step is > ok, or if we need try to work around it and still provide a caching > mechanism to background threads....
It's always safe to return null from the cache - it's just interpreted as a cache miss, and normal processing continues. Of course, it points out that the newsletter engine is going to hit the disk every time it does anything. Maybe that's not a problem most of the time, but I bet it is for bigger wikis. I wonder if it's kosher to store a reference to the Cache object to be used across threads? So I think it's reasonable to check in your workaround - Newsletters are broken without your fix. Although, come to think of it, I believe they worked for me at least once... ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Flexwiki-users mailing list Flexwiki-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flexwiki-users
