HTTP Semantics for Transactions and more
|Priority:||Should have||Due date:|
Currently the Repositories are all flushed on every request no matter the type. It should default to only PUT, POST DELETE updating the repositories.
GET Requests should schedule Transactions manually in the controller.
Additionally transactions should be encapsulated in one action and not executed over many different actions. This is problematic because there is no way to stop a transaction. Transactions should be rolled back (no flushing) when an exception is thrown in the controller.
[FEATURE] Persist after every controller invocation
Wire persistAll() from afterControllerInvocation instead of the
This is useful because it wraps all changes done in one dispatch in
a transaction, thus enabling better rollback in case of errors.
Updated by Karsten Dambekalns almost 2 years ago
- Project changed from TYPO3 Flow Base Distribution to TYPO3.Flow
Updated by Karsten Dambekalns over 1 year ago
- Target version set to 1.1
- Has patch set to No
Another point: action methods should be executed only of a matching request method comes in, e.g. a method declared for POST handling should only be callable by POST requests.
One more reason for this: http://googlewebmastercentral.blogspot.com/2011/11/get-post-and-safely-surfacing-more-of.html