Skip to main content

[websocket-spec issues] [JIRA] Updated: (WEBSOCKET_SPEC-101) Programmatic MessageHandler registration

  • From: "dannycoward (JIRA)" < >
  • To:
  • Subject: [websocket-spec issues] [JIRA] Updated: (WEBSOCKET_SPEC-101) Programmatic MessageHandler registration
  • Date: Sat, 2 Feb 2013 02:29:53 +0000 (GMT+00:00)
  • Auto-submitted: auto-generated


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

dannycoward updated WEBSOCKET_SPEC-101:
---------------------------------------

    Due Date: 05/Feb/13  (was: 01/Feb/13)

> Programmatic MessageHandler registration
> ----------------------------------------
>
>                 Key: WEBSOCKET_SPEC-101
>                 URL: http://java.net/jira/browse/WEBSOCKET_SPEC-101
>             Project: websocket-spec
>          Issue Type: Bug
>            Reporter: Pavel Bucek
>
> * Session.addMessageHandler and @WebSocketMessage specify different rules 
> (limits) to registered MessageHandlers. This should be unified if you want 
> to be able to achieve same results via programmatic and annotated case.
> * MessageHandler and Session javadoc sometimes mention "listener" instead 
> of "handler" when describing MessageHandler
> * Session.addMessageHandler does specify rules which are applicable to 
> MessageHandler.Basic (at least it seams to), what about 
> MessageHandler.Async (there is no specification of Async types)? It does 
> not mention "decodable" type at all.
> * Threading issues needs to be resolved (still TBDs in javadoc)

-- 
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-101) Programmatic MessageHandler registration

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