HTML Container Cache: How can we know if a cache skeleton or fragments is 
reused or not
---------------------------------------------------------------------------------------

                 Key: ESI-407
                 URL: http://www.jahia.net/jira/browse/ESI-407
             Project: Jahia Cache Systems (ESI / HTML Container Cache/ Back-end 
Caches)
          Issue Type: Sub-task
          Components: HTML Container Cache
    Affects Versions: Jahia Cache Server 6.0
         Environment: 23408
            Reporter: Stephane Croisier
            Assignee: Cédric Mailleux
            Priority: Major
             Fix For: Jahia Cache Server 6.0


How can we know (e.g in the console) if a cache skeleton or some fragments are 
reused or not. In the console there is no indication of the "sharing" of 
skeletong or fragments like it was the case with ESI. So when logued with two 
users belonging to the same group (read-only access), you have no indication in 
the console if the hit generates a new skeletong or is trying to "group" 
skeleton and reuse fragment.

Perhaps we could indicate it better. In ESI it was a bit too verbose as it was 
one line on a per fragment basis. But perhaps we could make one single line 
which say which ACL group key it is using at the page level and how many 
fragments are reused from cache (e.g 5 on 10 reused fragments). This would 
already let us know that some fragments are always missing and that there is 
perhaps a sharing issue...

Finally the cache toolbar is not available for such users (logued in 
read-only). So how can we debug them if the cache/debug mode in the url is not 
present any more?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://www.jahia.net/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
_______________________________________________
jira_list mailing list
[email protected]
http://lists.jahia.org/cgi-bin/mailman/listinfo/jira_list

Reply via email to