On May 15, 2009, at 6:07 PM, Eli Bach wrote:
Is there a better way to do this, other than to tell the user to
wait 30 minutes?
There's:
1) restart the whole DCS server
2) get the memcached to empty itself of all cached entries
3) get the memcached to empty itself of just the cached entries
related to modified entries (either added, removed or modified)
I'll probably look at doing 2, as doing 3 requires matching exactly
how DCS caches each bit of data, as well as need both the original
and the updated values for all the entries that DCS uses to handle
it properly.
You can lower the "cacheTimeout" value in the config file from 30
some something shorter, if the performance of that isn't a problem for
you. Shouldn't be if you aren't serving oodles of users.
-wsv
_______________________________________________
calendarserver-dev mailing list
calendarserver-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/calendarserver-dev
