[ 
https://issues.apache.org/jira/browse/JCS-195?focusedWorklogId=261010&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-261010
 ]

ASF GitHub Bot logged work on JCS-195:
--------------------------------------

                Author: ASF GitHub Bot
            Created on: 16/Jun/19 10:12
            Start Date: 16/Jun/19 10:12
    Worklog Time Spent: 10m 
      Work Description: sebbASF commented on pull request #4: JCS-195 Update 
element attributes size on serialization
URL: https://github.com/apache/commons-jcs/pull/4
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

            Worklog Id:     (was: 261010)
            Time Spent: 10m
    Remaining Estimate: 0h

> Update element attributes size on serialization
> -----------------------------------------------
>
>                 Key: JCS-195
>                 URL: https://issues.apache.org/jira/browse/JCS-195
>             Project: Commons JCS
>          Issue Type: Improvement
>          Components: Composite Cache
>    Affects Versions: jcs-2.2
>            Reporter: quietmint
>            Assignee: Thomas Vandahl
>            Priority: Major
>              Labels: admin-interface, beginner, documentation, easyfix, 
> pull-request-available
>             Fix For: jcs-3.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> {{ElementAttributes}} class has a field to store the size in bytes (e.g., for 
> use in an admin-style page). Calculating the size is an expensive operation, 
> so it makes sense to save the size whenever we serialize the element. Admin 
> pages that want this data could then get a cheap approximation from the last 
> time the element was serialized.
> Additionally, the javadocs say the size field is populated as -1 by default, 
> but it's really 0 by default.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to