jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-2619) improved internal representation of DATE values
Date Tue, 27 Apr 2010 11:10:31 GMT

    [ https://issues.apache.org/jira/browse/JCR-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12861362#action_12861362
] 

Thomas Mueller commented on JCR-2619:
-------------------------------------

> a 64-bit long is quite enough

Yes, if we restrict the year / don't support weird time zones. For me it's not a problem,
but for some applications it may be.

> 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.


Mime
View raw message