I've done some minor testing and everything seems to be working well. This is a great improvement in Silva performance.
I notice one thing from watching the cache manager statistics at /[mySilva]/service_static_cache_manager/manage_stats, the /[mySilva]/service_views/Silva/edit/VersionedContent/kupustyles.css seems to get hit every time you go to a document for the first time. Not a huge problem, but I wonder why because it does have a metadata file. Actually after playing with this for a while, I bet I know why: it's being acquired and so the path is different. The same thing happens if one goes to /globals/globals/up.gif
Do you think the title of the service is appropriate?
"Cache Manager for static non-silva objects"
or
"Cache Manager for static file-system objects"?
I've done some minor testing and everything seems to be working well. This is a great improvement in Silva performance.
I notice one thing from watching the cache manager statistics at /[mySilva] /service_ static_ cache_manager/ manage_ stats, the /[mySilva] /service_ views/Silva/ edit/VersionedC ontent/ kupustyles. css seems to get hit every time you go to a document for the first time. Not a huge problem, but I wonder why because it does have a metadata file. Actually after playing with this for a while, I bet I know why: it's being acquired and so the path is different. The same thing happens if one goes to /globals/ globals/ up.gif
Do you think the title of the service is appropriate?
"Cache Manager for static non-silva objects"
or
"Cache Manager for static file-system objects"?