[ https://issues.jboss.org/browse/ISPN-5298?page=com.atlassian.jira.plugin.... ] Galder Zamarreño edited comment on ISPN-5298 at 3/18/15 11:26 AM: ------------------------------------------------------------------ Ion, did you get a reply to the JSR issue? I'd wait to get an answer for that before making any immediate changes :| If we really need to implement this, I think Dan's approach is easiest. IOW, adding flags indicating the granularity of the expiration parameter. Seconds and Milliseconds would be enough. Remember what the protocol says: bq. Number of seconds that a entry during which the entry is allowed to life. If number of seconds is bigger than 30 days, this number of seconds is treated as UNIX time and so, represents the number of seconds since 1/1/1970. If set to 0, lifespan is unlimited. Seconds is enough to be able to represent any other expiration that's above it. Let's not complicate things beyond what's required :) was (Author: galder.zamarreno): Ion, did you get a reply to the JSR issue? I'd wait to get an answer for that before making any immediate changes :| If we really need to implement this, I think Dan's approach is easiest. IOW, adding flags indicating the granularity of the expiration parameter. Seconds and Milliseconds would be enough. Also, remember what the protocol says: bq. Number of seconds that a entry during which the entry is allowed to life. If number of seconds is bigger than 30 days, this number of seconds is treated as UNIX time and so, represents the number of seconds since 1/1/1970. If set to 0, lifespan is unlimited. Seconds is enough to be able to represent any other expiration that's above it. Let's not complicate things beyond what's required :) -- This message was sent by Atlassian JIRA (v6.3.11#6341)