Loading...

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XML

Word

Printable

Type: Enhancement
Resolution: Obsolete
Priority: Major
Fix Version/s: None
Affects Version/s: None
Component/s: Remote Protocols
Labels:
- REST

This JIRA is meant to act as an umbrella for improvements we might want to do in the REST protocol. For example:

As shown in ~~ISPN-1285~~ and https://docs.jboss.org/author/display/ISPN/Accessing+data+in+Infinispan+via+RESTful+interface, the use of 0 as timeToLiveSeconds and/or maxIdleTimeSeconds parameter(s) is not very intuitive and it's not even symmetric. This should be sorted out. This has been highlighted again in ~~ISPN-1425~~. One option could be to use -2 as @DefaultValue in order to distinguish between no values given and other options.

This JIRA should also figure out how to support multiple REST protocol versions.

is incorporated by

ISPN-8535 Rest API redesign

Closed

is related to

ISPN-1285 Cache entries stored via Hot Rod client with default expiry remain in cache

Closed

relates to

ISPN-1425 Incorrect settings [timeToLiveSeconds,maxIdleTimeSeconds] when default in REST

Resolved

ISPN-2810 In REST, default values for maxIdleTimeSeconds and timeToLiveSeconds should be 0

Closed

Assignee:: Galder Zamarreño

Reporter:: Galder Zamarreño

Archiver:: Amol Dongare

Created:: 2011/08/04 3:40 AM

Updated:: 2018/09/14 7:58 AM

Resolved:: 2018/09/14 7:58 AM

Archived:: 2024/11/28 6:21 AM