mercredi 20 avril 2016

Processors and presenters in the Orchestra Platform

I am going to develop an application which is built on the Laravel and the Orchestra Platform and my issue is directly associated with the last one. First of all, why do presenters are initialized inside processors instead of controllers? I am believed that presenters should be bind inside controllers instead of processors because of different requests ex. API. Would you explain me some use cases when this approach is better than I have thought?

The second issue is about providing listeners (interfaces, controllers) as a parameter to a processor inside controllers. As I have written before I would like to see a use case where this way is better than popular MVC design pattern. Why a processor method returns response using a listener (interfaces, controllers)? How will it be handled a response for different request which can be sent using an API?

Aucun commentaire:

Enregistrer un commentaire