Skip to main content

[websocket-spec issues] [JIRA] Updated: (WEBSOCKET_SPEC-117) Provide way to inform developers when connections timeout or close (without close frames being sent)

  • From: "dannycoward (JIRA)" < >
  • To:
  • Subject: [websocket-spec issues] [JIRA] Updated: (WEBSOCKET_SPEC-117) Provide way to inform developers when connections timeout or close (without close frames being sent)
  • Date: Sat, 2 Feb 2013 02:31:53 +0000 (GMT+00:00)
  • Auto-submitted: auto-generated


     [ 
http://java.net/jira/browse/WEBSOCKET_SPEC-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

dannycoward updated WEBSOCKET_SPEC-117:
---------------------------------------

    Due Date: 05/Feb/13

> Provide way to inform developers when connections timeout or close (without 
> close frames being sent)
> ----------------------------------------------------------------------------------------------------
>
>                 Key: WEBSOCKET_SPEC-117
>                 URL: http://java.net/jira/browse/WEBSOCKET_SPEC-117
>             Project: websocket-spec
>          Issue Type: Improvement
>            Reporter: dannycoward
>
> I can't see how the endpoint can be notified that its connection has timed 
> out (or disconnected w/o a close.)
> Should there be a CloseCodes.TIMEOUT (or READ/WRITE_TIMEOUT), and 
> CloseCodes.CONNECTION_DISCONNECT?
> Or should there be some exceptions for @WebSocketError like 
> WebSocketTimeoutException (or WebSocketRead/WriteTimeout) and 
> WebSocketDisconnectException. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://java.net/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


[websocket-spec issues] [JIRA] Updated: (WEBSOCKET_SPEC-117) Provide way to inform developers when connections timeout or close (without close frames being sent)

dannycoward (JIRA) 02/02/2013
 
 
Close
loading
Please Confirm
Close