[TYPO3-team-templavoila] Store configuration (DS, etc.) in other format than XML in database

[Niels Fröhling]

Hy;

Jigal asked for the following:

 > As Fabrizio has shown with his measurements a TV page requires many xml2array 
 > conversions. While his caching proposal helps a lot, the real problem is the
 > very expensive xml2array conversion.
 > A different storage format (serialized array, json, ...) may be more
 > efficient.
 >
 > For interaction with the programmer/site builder XML could still be used;
 > array2xml then only needs to be used inside the editing parts.

Well here just a breakdown of the data and their formats:

* DS (dataprot) ->
    T3DataStructure ->
     XML ->
      because it's a flexform (and need to be human editable)
* TO (localprocessing) ->
    T3DataStructure ->
     XML ->
      because it's a flexform (and need to be human editable)
* TO (templatemapping) ->
    Mapping-Array (Head) ->
     serialized
* TO (templatemapping) ->
    Mapping-Array (Body) ->
     serialized
* TO (templatemapping) ->
    Template-Source (cached HTML) ->
     HTML ->
      serialized
* Page (tx_templavoila_flex) ->
    T3Flexform ->
     XML ->
      because it's the flexform's result

The chain is basically this:

       +-> DS overlay TO ->
       |     TCE-FF (datastructure) ->
       |       interaction ->
       |         TCE-FF (flexform)
       |                |
       |                |
HTML -+                +------- substitution of FF-values |
       |                |        through the mapping information |
       |                |        into the HTML-source
       |                |                 |
       |                |                 +----> output
       |                |
       |                |
       +-> Mapping information


The conclusion is that there is actually not much XML involved, only the 
necessary to have a good time with core-flexforms.
But that doesn't mean there is no other non-XML redundancy hidden somewhere ...

Ciao
   Niels