[TYPO3-mvc] SOAP call using extbase

[Jochen Rau]

Hi Masi.

On 11.04.10 21:16, Martin Kutschker wrote:
> Jochen Rau schrieb:
>> On 10.04.10 16:09, Bernhard Kraft wrote:
>>> Now this "resultAction" should perform the SOAP request. I guess the
>>> SOAP interface should get implemented as respository? Correct?
>>
>> I'd suggest to do so.

[...]

> To be honest this answer surprises me very much. Even when the remote system really persists the
> objects the local part can only be something like a facade. I agree that a RDBMS is not the only
> possible implementation of a repository, but I don't think that any remote system can act as a
> repository.

Why not? The *concept* of a repository doesn't depend on the reliability 
and performance of the storage backend it uses. A repository is in fact 
a facade (pattern). And how to prevent data loss is more a matter of how 
the backend is implemented. This could be indeed very challenging.

But I agree to some extend. I have emphasized the persistence aspect too 
much. How and where the interface to a SOAP service should be 
implemented is more a matter of the type of service it provides. It can 
provide a storage service (even read-only). But it can also provide a 
stateless, pure functional service (take a and b and perform a+b; give 
me the current date of mayan calendar). In the latter case I would 
implement it as a Domain Service.

> Hiding the fact that the storage is remote and the connection is unreliable may be nice. But IMHO
> it's not wise, because if you do you're hiding a crucial point when it comes to reliability and
> performance. *

> * To quote Evens from memory: "If your model cannot be implemented with good performance it's broken"

In Evans' book there is a small section about Performance Tuning. Maybe 
you are referring to this one?

Regards
Jochen