[infinispan-issues] [JBoss JIRA] Commented: (ISPN-1425) Incorrect settings [timeToLiveSeconds, maxIdleTimeSeconds] when default in REST

[Greg Autric (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-1425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631774#comment-12631774 ] 

Greg Autric commented on ISPN-1425:
-----------------------------------

I think we have to provide all posiblities :
* default one aka current cache configuration without any HTTP header 
* user wanna use (-1) infinite TTL
* user wanna use 0 TTL (maybe useless but needed)
* user wanna use an other TTL

we need a default value, we could use inside Server.scala a string value "DV" to switch with 
what do you think about ? maybe you have a better idea ?

> Incorrect settings [timeToLiveSeconds,maxIdleTimeSeconds] when default in REST 
> -------------------------------------------------------------------------------
>
>                 Key: ISPN-1425
>                 URL: https://issues.jboss.org/browse/ISPN-1425
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Cache Server
>    Affects Versions: 5.1.0.ALPHA1
>            Reporter: Greg Autric
>            Assignee: Galder Zamarreño
>             Fix For: 5.1.0.BETA2
>
>         Attachments: Server.scala.ISPN-1425.patch, Server.scala.ISPN-1425.v2.patch
>
>   Original Estimate: 2 hours
>  Remaining Estimate: 2 hours
>
> If HTTP client didn't use 
> timeToLiveSeconds or/and maxIdleTimeSeconds in all PUT/POST header request
> Cache entry will allways use -1 for timeToLiveSeconds and -1 for maxIdleTimeSeconds
> instead of current Cache settings

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira