Feature #33469

Task #36800: Streamline Resource object API

Support for temporary Resources

Added by Bastian Waidelich over 3 years ago. Updated about 2 years ago.

Status:Rejected Start date:2012-01-26
Priority:Should have Due date:
Assigned To:- % Done:

0%

Category:Resource
Target version:-
PHP Version: Complexity:
Has patch:No

Description

Currently all resources need a Database, because the resource manager uses it in order to store resource pointers.
It should be possible to work with resources without having to use the (doctrine) persistence layer.


Related issues

related to TYPO3.Flow - Feature #33587: Automatically remove unused Resources New 2012-02-01

History

#1 Updated by Robert Lemke over 3 years ago

  • Parent task set to #36800

#2 Updated by Robert Lemke about 2 years ago

  • Status changed from New to Rejected

With what we currently call "Resource" - that is, managed assets which are stored somewhere and published somewhere (else) - I don't see a way to work without a database or at least a file based database like sqlite.

Also available in: Atom PDF