Re: [aerogear-dev] Push Endpoints

On Thu, Jun 27, 2013 at 2:00 PM, Sebastien Blanc <scm.blanc(a)gmail.com&gt; wrote: Hum for both for me it should be an 200 OK with no reponse body. For the update is we have a 200 OK , it is the responsability of the client to do a GET to retrive the updated client Agree on the GET

On Thu, Jun 27, 2013 at 1:57 PM, Lucas Holmquist <lholmqui(a)redhat.com&gt; wrote: I've been looking at the endpoints of the push server a little more since coding the Admin UI, and i see that for "updates" and "deletes", the response is "no content" for example: https://github.com/aerogear/aerogear-unified-push-server/blob/master/src/... I wasn't sure what we should be returning here. I'd imagine for update we would want to return the update entity but what about for delete? In the case of deleting a "Push Application", should we return the new list of Push Applications? thoughts? _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev