Empty API response ?

[nfaugout-lucca]

We currently always return the entity when performing a POST or a PUT request.

We already return void for DELETE requests.

When POSTing, after the entity is created, we GET the entity again to be sure that the responded entity correspond a undred % with the one inside the database. It goes the same for PUT.

I wonder if we could just respond 200 OK or 201 Accepted, with the new location of the entity (in case of a POST).

If the JS client wants the new version of the entity, it could issue a new GET request.

This way, we can simplify a lot the code of the AppController and reduce responsibility issue between AppController and RestCollection.

[nfaugout-lucca]

This is part of a bigger change that consist of issuing more requests from the client, and to fit more with the original REST approach.

[nfaugout-lucca]

Je ferme cette Issue car j'en parle là : #258