[aerogear-dev] Push Endpoints

Matthias Wessendorf matzew at apache.org
Thu Jun 27 08:08:18 EDT 2013


On Thu, Jun 27, 2013 at 2:06 PM, Lucas Holmquist <lholmqui at redhat.com>wrote:

>
> On Jun 27, 2013, at 8:03 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>
>
>
> On Thu, Jun 27, 2013 at 2:00 PM, Sebastien Blanc <scm.blanc at gmail.com>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
>

yeah :-)





>
>
>
>>
>> On Thu, Jun 27, 2013 at 1:57 PM, Lucas Holmquist <lholmqui at redhat.com>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/main/java/org/jboss/aerogear/connectivity/rest/registry/applications/PushApplicationEndpoint.java#L117
>>>
>>>
>>> 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 at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at 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 at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20130627/55cb5c35/attachment.html 


More information about the aerogear-dev mailing list