[
https://issues.apache.org/jira/browse/OAK-2416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14336225#comment-14336225
]
Michael Dürig commented on OAK-2416:
------------------------------------
bq. I can create a new patch including the latest changes in your branch on
GitHub.
No need for a new patch. It's all in the branch.
In general I think it would be good if we could keep this work out of the
regular 1.1 release cycle until we figure out where we go with the
{{RevisionFactory}} approach. We could either continue working on the branch I
created or maybe better on a branch in your fork on Github so you'd have more
control and Alex and me could contribute through pull requests.
> Support continuable sessions
> -----------------------------
>
> Key: OAK-2416
> URL: https://issues.apache.org/jira/browse/OAK-2416
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Components: core
> Reporter: Michael Dürig
> Labels: api
> Attachments: OAK-2416-1.patch
>
>
> Implement support for continuable sessions to keeps state across multiple
> client/server interactions. Continuable sessions do not require any
> additional state on the server (i.e. Oak) apart form the apparent repository
> state.
> To continue a session a client would obtain a continuation token from the
> current session. This token can be used on the next call to
> {{Repository.login}} to obtain a new {{Session}} instance that is based on
> the same repository revision that the session the token was obtained from.
> Additionally the token could contain information re. authentication so
> subsequent request can go through a simplified authentication procedure.
> ([~asanso]'s work on OAuth might be of help here.)
> Transient changes are not supported in continuable sessions. Obtaining a
> continuation token from a session with transient changes results in an error.
> Continuable sessions are typically short lived (i.e. the time of a single
> HTTP request). Specifically continuable session do not retain the underlying
> repository revision from being garbage collected. Clients need to be able to
> cope with respective exceptions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
