Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 6679 invoked from network); 27 Apr 2010 12:13:55 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 27 Apr 2010 12:13:55 -0000 Received: (qmail 83101 invoked by uid 500); 27 Apr 2010 12:13:54 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 83038 invoked by uid 500); 27 Apr 2010 12:13:54 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 83031 invoked by uid 99); 27 Apr 2010 12:13:53 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Apr 2010 12:13:53 +0000 X-ASF-Spam-Status: No, hits=-1354.3 required=10.0 tests=ALL_TRUSTED,AWL X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Apr 2010 12:13:52 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o3RCDWdH001344 for ; Tue, 27 Apr 2010 12:13:32 GMT Message-ID: <2413262.32401272370412404.JavaMail.jira@thor> Date: Tue, 27 Apr 2010 08:13:32 -0400 (EDT) From: "Alexander Klimetschek (JIRA)" To: dev@jackrabbit.apache.org Subject: [jira] Issue Comment Edited: (JCR-2619) improved internal representation of DATE values In-Reply-To: <27638204.8601272292111967.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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.