Feature #28136

HTTP Semantics for Transactions and more

Added by Benjamin Eberlei over 10 years ago. Updated over 9 years ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
Persistence
Target version:
-
Start date:
2011-07-12
Due date:
% Done:

0%

Estimated time:
PHP Version:
Has patch:
No
Complexity:

Description

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.


Related issues

Related to TYPO3.Flow - Feature #27117: Bind routes to HTTP request methodsResolvedBastian Waidelich2011-05-292013-04-13

Actions
Precedes TYPO3.Flow - Feature #28137: Do not use clone in PersistentObject ParamConverterClosedKarsten Dambekalns2011-07-132011-07-13

Actions
#1

Updated by Karsten Dambekalns about 10 years ago

  • Project changed from TYPO3 Flow Base Distribution to TYPO3.Flow
#2

Updated by Karsten Dambekalns about 10 years ago

  • Category set to Persistence
#3

Updated by Karsten Dambekalns almost 10 years 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

#4

Updated by Karsten Dambekalns over 9 years ago

  • Target version deleted (1.1)

Also available in: Atom PDF