Merge branch 'release/1.0.0'
This commit is contained in:
commit
dc98be32c2
2 changed files with 28 additions and 1 deletions
13
README.md
Normal file
13
README.md
Normal file
|
@ -0,0 +1,13 @@
|
||||||
|
DigiComp.FlowSessionLock
|
||||||
|
------------------------
|
||||||
|
|
||||||
|
By default the session established by Flow is not "protected" in any way.
|
||||||
|
This package restricts every request to load the session only, if there are no other requests having it in access currently.
|
||||||
|
It allows to set custom pointcut which will set the session in "ReadOnly" mode, which allows concurrent requests to read, but disallows the current request to write the session.
|
||||||
|
|
||||||
|
If you want to allow concurrent access somewhere, you can add your trigger pointcut in Settings.yaml like such:
|
||||||
|
|
||||||
|
DigiComp:
|
||||||
|
FlowSessionLock:
|
||||||
|
readOnlyExpressions:
|
||||||
|
'AcmeLock': 'method(Acme/SuperPackage/Controller/ConcurrentController->concurrentAction())'
|
|
@ -1,7 +1,21 @@
|
||||||
{
|
{
|
||||||
"name": "digicomp/flowsessionlock",
|
"name": "digicomp/flowsessionlock",
|
||||||
"description": "Sesion locking for Neos Flow",
|
|
||||||
"type": "neos-package",
|
"type": "neos-package",
|
||||||
|
"description": "Sesion locking for Neos Flow - it secures the session becoming corrupted by concurrent access to the same session by different requests",
|
||||||
|
"keywords": [
|
||||||
|
"flow",
|
||||||
|
"neos"
|
||||||
|
],
|
||||||
|
"authors": [
|
||||||
|
{
|
||||||
|
"name": "Ferdinand Kuhl",
|
||||||
|
"email": "f.kuhl@digital-competence.de",
|
||||||
|
"homepage": "http://www.digital-competence.de",
|
||||||
|
"role": "Developer"
|
||||||
|
}
|
||||||
|
],
|
||||||
|
"license": "MIT",
|
||||||
|
"homepage": "https://github.com/digicomp/DigiComp.FlowSessionLock",
|
||||||
"require": {
|
"require": {
|
||||||
"neos/flow": "^6.2",
|
"neos/flow": "^6.2",
|
||||||
"php": "^7.4",
|
"php": "^7.4",
|
||||||
|
|
Loading…
Reference in a new issue