[aerogear-dev] [SimplePush] Close status codes

[Kris Borchers]

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.

On Jun 4, 2013, at 6:32 AM, Daniel Bevenius <daniel.bevenius at gmail.com> wrote:

> Simple Push Error codes
> 
> 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:
> 
> c[3039,"Connection closed due to inactivity"]
> 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 SimplePush Protocol Specification yet, and thought I bring this up for discussion.
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20130604/b8a190ac/attachment.html