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 12:21:31 GMT

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

Thomas Mueller commented on JCR-2619:

> It should support all values that a Calendar object can have

If we want to do that, then a "long" is not enough. Even long+int is not enough, because a
java.util.TimeZone (which is used internally in each java.util.Calendar) is not just an offset,
but also includes rules.

If we want to support each possible java.util.Calendar, then we either need to use a String
or store the Calendar object.

If we only want to support possible values according to the JCR 2.0 specification (this I'm
not sure), then a long is enough, for example in the format yyyymmddhhMMssMMMZZZZ.

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

View raw message