<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Sep 21, 2013 at 7:18 AM, Daniel Bevenius <span dir="ltr"><<a href="mailto:daniel.bevenius@gmail.com" target="_blank">daniel.bevenius@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">This is no problem as we currently always replay with "{}". I'll remove support for anything but the simple "{}" too. <div>
<br></div><div>Sounds great having dev-simplepush@mozilla for things like this.</div>
<div>Thanks for the heads up!<br></div></div></blockquote><div><br></div><div>yeah, great to see !</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">
<div></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On 20 September 2013 22:00, JR Conlin <span dir="ltr"><<a href="mailto:jrconlin@gmail.com" target="_blank">jrconlin@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Yep, every ping of "{}" would return a ping of "{}". The discussion over<br>
here was a bit ... heated. Partly because I wanted to make sure that<br>
this is the ONLY last minute change, and I think I can say it is. I<br>
won't alter the published spec until I get the OK from y'all, but I'll<br>
probably go ahead and alter the server to return the abbreviated ping.<br>
(Now I get to tell QA and Ops they'll need to fix up their tests, yay!)<br>
<br>
Honestly, I'm not a huge fan of having app level pings. These really do<br>
need to live at the net level since they're already spec'd out in<br>
Websocket, and FAR lighter weight, but there are significant issues<br>
there and we play what we're dealt.<br>
<br>
I've also filed a bug to get dev-simplepush@mozilla set up. I'm fine<br>
with posting here as well, but as the consumers and providers grow, I'd<br>
like to have a central place we can announce crap like this.<br>
<br>
I'll send a follow up once the mail list is live for anyone interested<br>
in joining.<br>
<div><div><br>
On 2013/9/20 12:38 PM, Kris Borchers wrote:<br>
> 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.<br>
><br>
>> On Sep 20, 2013, at 13:55, JR Conlin <<a href="mailto:jrconlin@gmail.com" target="_blank">jrconlin@gmail.com</a>> wrote:<br>
>><br>
>> Hi all,<br>
>><br>
>> We got a rather late request from a partner that changes how Ping<br>
>> responses act.<br>
>><br>
>> While the spec says that a ping response is arbitrary and it's<br>
>> recommended that the server reply with "{}", a partner is requesting<br>
>> that this be the only response from a server for a Ping.<br>
>><br>
>> The partner has client deployed code, which is the only reason we're<br>
>> entertaining the change.<br>
>><br>
>> Would this change be a significant impact to your server, testing or<br>
>> operations?<br>
>><br>
>> Thanks!<br>
>> _______________________________________________<br>
>> aerogear-dev mailing list<br>
>> <a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
> _______________________________________________<br>
> aerogear-dev mailing list<br>
> <a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
</div></div></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Matthias Wessendorf <br>
<br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div></div>