[TYPO3-ect] RFC: Result Browser Service for lib/div - part 1 + 2

[Elmar Hinz]

Hi Daniel,

Daniel Brüßler wrote:

> Hello Elmar,
> 
> The definition looks very good! Just some thoughts from me about the RFC.
> 
> == version of the interface ==
> for me versioning is important:
> 
> ---
> required getInterfaceVersion

O.K. That's added. 

Is there a standard how interfaces should be versionized?

> ---
> 
> So an extension-developer could use it like this:
> * get the service-reference for a result-browser
> * no rendering for a result-browser what just has an outdated
> interface-version
> * light rendering by a simple version
> * full rendering by a super-duper version

Right. That's part 3 or part 4. Defining the selection criteria of the
service if multiple implementations are available.

> 
> 
> == optional functions ==
> What do you think about a function like "function_exists" what we know
> from PHP itself?

Hm, that's the part of the caller of to service do this. Right?

> 
> 
> == choose one of many ==
> Is ist possible to choose a special rendering-service by its subtype -
> for example "resultBrowserAjax"? When that special is not available a
> standard rendering-service should be given as reference.

Right. That's part 3 or part 4. Defining the selection criteria of the
service if multiple implementations are available.


Regards

Elmar