<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I thought we discussed that you could detect that the connection was still active and we wouldn't close it in that case. Did you decide against that? I can still see situations where we would need to handle a close frame on the client but I thought we decided to not do it in this case.<div><br><div><div>On Jun 4, 2013, at 6:32 AM, Daniel Bevenius <<a href="mailto:daniel.bevenius@gmail.com">daniel.bevenius@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><h2 style="margin-right: 0px; margin-bottom: 15px; margin-left: 0px; padding: 0px; font-size: 2em; border-bottom-width: 1px; border-bottom-style: solid; border-bottom-color: rgb(238, 238, 238); font-family: Helvetica, arial, freesans, clean, sans-serif; margin-top: 0px !important; ">
Simple Push Error codes</h2><p style="margin: 15px 0px; font-family: Helvetica, arial, freesans, clean, sans-serif; font-size: 15px; line-height: 25px; ">I'd like to bring up a question that came up while developing the SimplePush Server. The server has a scheduled job that will clean up inactive UserAgents. When it does the clean up, the connection will also be closed by the server (if it is still active) and an error code with a message is returned. This will be a SockJS close frame which looks like this:</p>
<div class="" style="border: 0px; padding: 0px; font-family: Helvetica, arial, freesans, clean, sans-serif; font-size: 15px; line-height: 25px; "><pre style="font-size:13px;line-height:19px;font-family:Consolas,'Liberation Mono',Courier,monospace;word-wrap:break-word;margin-top:15px;margin-bottom:15px;background-color:rgb(248,248,248);border:1px solid rgb(221,221,221);overflow:auto;padding:6px 10px;border-top-left-radius:3px;border-top-right-radius:3px;border-bottom-right-radius:3px;border-bottom-left-radius:3px"><span class="">c</span><span class="">[</span><span class="" style="color:rgb(0,153,153)">3039</span><span class="">,</span><span class="" style="color:rgb(221,17,68)">"Connection closed due to inactivity"</span><span class="">]</span>
</pre></div><p style="margin-top: 15px; margin-right: 0px; margin-left: 0px; font-family: Helvetica, arial, freesans, clean, sans-serif; font-size: 15px; line-height: 25px; margin-bottom: 0px !important; ">Now, the status code which is the first entry above is just something I made up. It might be nice to have a few different error codes to signal to the client the reason for closing, as the client might want to take some action. I've not found anything in the <a href="https://wiki.mozilla.org/WebAPI/SimplePush/Protocol" style="color:rgb(65,131,196);text-decoration:none">SimplePush Protocol Specification</a> yet, and thought I bring this up for discussion.</p>
</div>
_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/aerogear-dev</blockquote></div><br></div></body></html>