[aerogear-dev] [simplepush] Proposed change to Ping response

[Matthias Wessendorf]

On Sat, Sep 21, 2013 at 7:18 AM, Daniel Bevenius
<daniel.bevenius at gmail.com>wrote:

> This is no problem as we currently always replay with "{}". I'll remove
> support for anything but the simple "{}" too.
>
> Sounds great having dev-simplepush at mozilla for things like this.
> Thanks for the heads up!
>

yeah, great to see !


>
>
> On 20 September 2013 22:00, JR Conlin <jrconlin at gmail.com> wrote:
>
>> Yep, every ping of "{}" would return a ping of "{}". The discussion over
>> here was a bit ... heated. Partly because I wanted to make sure that
>> this is the ONLY last minute change, and I think I can say it is. I
>> won't alter the published spec until I get the OK from y'all, but I'll
>> probably go ahead and alter the server to return the abbreviated ping.
>> (Now I get to tell QA and Ops they'll need to fix up their tests, yay!)
>>
>> Honestly, I'm not a huge fan of having app level pings. These really do
>> need to live at the net level since they're already spec'd out in
>> Websocket, and FAR lighter weight, but there are significant issues
>> there and we play what we're dealt.
>>
>> I've also filed a bug to get dev-simplepush at mozilla set up. I'm fine
>> with posting here as well, but as the consumers and providers grow, I'd
>> like to have a central place we can announce crap like this.
>>
>> I'll send a follow up once the mail list is live for anyone interested
>> in joining.
>>
>> On 2013/9/20 12:38 PM, Kris Borchers wrote:
>> > I think we would be fine with that. Dan would be the best one to answer
>> but he is on CET and probably sleeping. I know our client only sends '{}'
>> in its pings and the server handles that so if I'm understanding correctly,
>> what you want is for the server to only respond to that payload in a ping
>> which again, I think should be fine.
>> >
>> >> On Sep 20, 2013, at 13:55, JR Conlin <jrconlin at gmail.com> wrote:
>> >>
>> >> Hi all,
>> >>
>> >> We got a rather late request from a partner that changes how Ping
>> >> responses act.
>> >>
>> >> While the spec says that a ping response is arbitrary and it's
>> >> recommended that the server reply with "{}", a partner is requesting
>> >> that this be the only response from a server for a Ping.
>> >>
>> >> The partner has client deployed code, which is the only reason we're
>> >> entertaining the change.
>> >>
>> >> Would this change be a significant impact to your server, testing or
>> >> operations?
>> >>
>> >> Thanks!
>> >> _______________________________________________
>> >> 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
>>
>> _______________________________________________
>> 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/20130921/8d675efa/attachment-0001.html