[TYPO3-ect] RFC: Namings and addressing data of the pipeline

[Daniel Brüßler]

Hello Elmar,

really needed that we find easy names. ;-)

== tree of plugins ==
> a) Describing the PAC tree as a "tree of plugins":
> 
> All nodes have the typical interface of plugins of the tslib_pibase type:
> 
> $outputString = $Plugin->main($inputString, $configuration);
> 
> This definition includes user defined content elements, widgegts, parser,
> etc.

"tree of plugins" aka TOP:
yes!! With that definition we
* "catch" the task what an "extension" is (one or more plugins, addional 
one or more services, additional one or more XCLASSes)
* "give" the concept of extendability, because one can "through in" a 
new "plugin" (renderer, widget, service, extended SQL-queries, 
html-skins, new features for the main-extension) so that it gets into 
the whole tree.

== the actions ==
> b) Descibing the actions as "pipeline of processors":
> 
> We called that "action chain" before. It results in the acronym "PLOP".

not good IMHO. why not "workflow", "action chain", "pipeline" or 
"pipeline elements"?

== processor ==
That sounds to big INMHO. something like "action", "task", "job", 
"workflow-item" sounds better.

== long or short ==
> c) A shorter name for the single processor element could be useful but is
> Instead of long.        tx_lib_resultBrowserProcessor
> Something shorter like: tx_lib_resultBrowserPlp
>     tx_lib_resultBrowserController
>     tx_lib_resultBrowserModel
>     tx_lib_resultBrowserView

Good that it's not "tx_lib_resultBrowser_C", "tx_lib_resultBrowser_M", 
"tx_lib_resultBrowser_V". Also here there shouldn't be such a shortname.


== Addressing data of the pipeline ==
> (...) SPL (...) It comes to limits, when list data plus string data needs to
> be piped, for example a result list and the ouptput string of the
> resultbrowser.

from Bananas-documentation in wiki:
The function makeProcessor() of the controller does those things that 
are typically done for processor objects of the action pipe. It 
especially pipes the internal array content from one processor to the 
next. In the action pipe the model, the resultbrowser and the view are 
created and processed

There you write that the internal array content will be given from one 
processor to the next. Normally it's no problem to add a new 
array-element what contains a string. Why isn't that possible in this 
case? For example $internalArray['content_ResultBrowser'] = 'xyz'

kind regards
Daniel