oh, and this is where i started creating the UI, trying out ember, so things are still in flux https://github.com/lholmquist/aerogear-unified-push-server-admin-ui/tree/...

On Jun 27, 2013, at 7:57 AM, 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

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

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

On Jun 27, 2013, at 8:03 AM, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: 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 Thats fine, i wasn't sure what was the "correct" way of doing it. I'll create a JIRA to update the response to return OK. should be a pretty easy PR

> > 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 _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

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 yes, that could be an option. I am fine with that but what about for delete? In the case of deleting a "Push Application", should we return the new list of Push Applications? I think... 204 does match the "HTTP spec". But I am OK with receving something else :-)

List off all remaining PushApps, for that user? Not sure :) thoughts? _______________________________________________ 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