[TYPO3-core] RFC #16414: Integration of a File Abstraction Layer into TYPO3

[Andreas Wolf]

This is an SVN patch request.

Type: New feature

Bugtracker references:
http://bugs.typo3.org/view.php?id=16414

Branches:
trunk

Problem:
The project has been introduced at the Developer Days this year in Elmshorn.

The goal of the FAL is to provide an abstraction for the file system for
easier usage of files, esp. with respect to Digital Asset Management.
Additionally, this project would allow site owners to get rid of the
uploads/ folder with is currently cluttered with lots of files on larger
installations. There is also the aim to provide additional services
around files, e.g. metadata extraction or file processing - but this is
out of scope for this project.

This RFC provides the basis for the file abstraction layer, i.e. the
basic functionality inside the Core and a system extension for enabling
the FAL.

Additionally, there is an integration for a new uploader called plupload
(www.plupload.com).


The attached patch consists of four parts:

 - fal_core.patch: The core parts of FAL (in typo3/ and t3lib/)
 - fal_unittest.patch: Unit tests for the core parts
 - fal_filelist.patch: Changes to sysext filelist
 - T3X_fal: System extension for FAL integration

Additionally, you need to put the plupload stuff from www.plupload.com
into typo3/contrib/plupload/

The TYPO3 FAL tree is also available at
http://github.com/t3dev/typo3v4core/tree/fileabstractionlayer


Notes:
These patches are the outcome of the Code Sprint in Düsseldorf at wmdb
last weekend. We are aware that this is not a complete solution to all
File Abstraction needs, but it serves as a good base for further
development. The FAL team will continue working on this - the following
things are - among others - currently planned: support for all required
file operations, either remote or local; support for additional storage
backends (Amazon S3, other CDNs); a migration wizard for migrating
existing fields to FAL; and many other cool things ;-)


Regards
Andreas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0016414_fal_core.patch
Type: text/x-patch
Size: 126969 bytes
Desc: not available
URL: <http://lists.typo3.org/pipermail/typo3-team-core/attachments/20101116/1c04d774/attachment-0003.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0016414_fal_filelist.patch
Type: text/x-patch
Size: 26513 bytes
Desc: not available
URL: <http://lists.typo3.org/pipermail/typo3-team-core/attachments/20101116/1c04d774/attachment-0004.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0016414_fal_unittest.patch
Type: text/x-patch
Size: 18410 bytes
Desc: not available
URL: <http://lists.typo3.org/pipermail/typo3-team-core/attachments/20101116/1c04d774/attachment-0005.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0016414_T3X_fal-0_0_0-z-201011161019.t3x
Type: application/octet-stream
Size: 35268 bytes
Desc: not available
URL: <http://lists.typo3.org/pipermail/typo3-team-core/attachments/20101116/1c04d774/attachment-0001.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 258 bytes
Desc: OpenPGP digital signature
URL: <http://lists.typo3.org/pipermail/typo3-team-core/attachments/20101116/1c04d774/attachment-0001.pgp>