>Basically you set a default in seconds for the HTML results to be
>cached, and then have triggers set that force the cache to regenerate
>(whenever CRUD happens to the content, for example).
>
>Can't speak for Perl/Python/Ruby/.Net/Java, but Cache_Lite sure made a
>believer out of me!
>
>
>
Nice to have it in a library, but if you want to be that simplistic then
it's easy in any language. What if a process on server B modifies a n
important value that server A has cached though? Coherency (albeit that
the client may choose to not use it) is a must for a general solution.