[Red Hat JIRA] (ISPN-12746) Spring Session Repository should implement ReactiveSessionRepository
by Dan Berindei (Jira)
Dan Berindei created ISPN-12746:
-----------------------------------
Summary: Spring Session Repository should implement ReactiveSessionRepository
Key: ISPN-12746
URL: https://issues.redhat.com/browse/ISPN-12746
Project: Infinispan
Issue Type: Enhancement
Components: Spring Integration
Affects Versions: 12.0.1.Final
Reporter: Dan Berindei
[ReactiveSessionRepository|https://docs.spring.io/spring-session/docs/2.4.2/reference/html5/#api-reactivesessionrepository] allows the session repository to fetch/save sessions without blocking, so it can be used in reactive applications.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 10 months
[Red Hat JIRA] (ISPN-12745) Elytron 1.14.2
by Tristan Tarrant (Jira)
Tristan Tarrant created ISPN-12745:
--------------------------------------
Summary: Elytron 1.14.2
Key: ISPN-12745
URL: https://issues.redhat.com/browse/ISPN-12745
Project: Infinispan
Issue Type: Component Upgrade
Components: Dependency, Security
Affects Versions: 12.0.1.Final
Reporter: Tristan Tarrant
Assignee: Tristan Tarrant
Fix For: 12.1.0.Dev01
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 10 months
[Red Hat JIRA] (ISPN-12744) Spring Session Repository should replicate only changed attributes
by Dan Berindei (Jira)
Dan Berindei created ISPN-12744:
-----------------------------------
Summary: Spring Session Repository should replicate only changed attributes
Key: ISPN-12744
URL: https://issues.redhat.com/browse/ISPN-12744
Project: Infinispan
Issue Type: Enhancement
Components: Spring Integration
Affects Versions: 12.0.1.Final
Reporter: Dan Berindei
bq. During the lifecycle of an HTTP request, the HttpSession is typically persisted to SessionRepository twice. The first persist operation is to ensure that the session is available to the client as soon as the client has access to the session ID, and it is also necessary to write after the session is committed because further modifications to the session might be made. Having this in mind, we generally recommend that a SessionRepository implementation keep track of changes to ensure that only deltas are saved. This is particularly important in highly concurrent environments, where multiple requests operate on the same HttpSession and, therefore, cause race conditions, with requests overriding each other's changes to session attributes. All of the SessionRepository implementations provided by Spring Session use the described approach to persist session changes and can be used for guidance when you implement custom SessionRepository.
https://docs.spring.io/spring-session/docs/2.4.2/reference/html5/#custom-...
Our {{AbstractInfinispanSessionRepository}} saves the entire set of attributes of attributes, even if the only thing being updated is the last access timestamp (see {{updateTTL()}}. We could use functional commands (directly when the cache is embedded, via server-side tasks when the cache is remote) to replicate only the subset of created/modified/removed attributes. We should also investigate using our native max-idle support for TTL.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 10 months
[Red Hat JIRA] (ISPN-12743) Jackson 2.12.1
by Tristan Tarrant (Jira)
Tristan Tarrant created ISPN-12743:
--------------------------------------
Summary: Jackson 2.12.1
Key: ISPN-12743
URL: https://issues.redhat.com/browse/ISPN-12743
Project: Infinispan
Issue Type: Component Upgrade
Components: Dependency
Affects Versions: 12.0.1.Final
Reporter: Tristan Tarrant
Assignee: Tristan Tarrant
Fix For: 12.1.0.Dev01
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 10 months