[
https://issues.jboss.org/browse/ISPN-1425?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-1425:
----------------------------------------
Option 1 can be achieved passing 0 for timeToLiveSeconds and maxIdleTimeSeconds
Option 2 can be achieved by passing nothing
What's the use case for option 3? :)
Option 4 covered
Also, your suggest of default value won't work cos it needs to be compatible with the
type, so "DV" won't work.
FYI, we're expecting to look into the handling of these parameters for Infinispan 6.0,
but right now we cannot make modifications of the REST Api. For more info see ISPN-1307.
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
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira