[
https://issues.apache.org/jira/browse/JCR-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12861380#action_12861380
]
Alexander Klimetschek edited comment on JCR-2619 at 4/27/10 8:12 AM:
---------------------------------------------------------------------
It should support all values that a Calendar object can have, including any
timezone offset. The maximum that I know is +14, so having the timezone running
from -15h to +15h, which would be -900 to +900 minutes, should cover every case.
http://www.worldtimezone.com/faq.html
was (Author: alexander.klimetschek):
It should support all values that a Calendar object can have, including any
timezone offset. The maximum that I know is +14, so having the timezone running
from -15h to +15h, which would be -900 to +900 minutes, should cover every case.
> improved internal representation of DATE values
> -----------------------------------------------
>
> Key: JCR-2619
> URL: https://issues.apache.org/jira/browse/JCR-2619
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core, jackrabbit-spi-commons
> Reporter: Stefan Guggisberg
> Fix For: 2.2.0
>
> Attachments:
> JCR-2619_improved_internal_representation_of_DATE_values.patch
>
>
> DATE values are currently internally represented as java.util.Calendar
> objects.
> Calendar objects have a huge memory footprint (approx 200bytes per instance)
> and are mutable.
> i suggest to replace the internal DATE representation with a ISO8601 format
> string
> (immutable and approx. 85-90% smaller footprint).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
