websocket-spec
  1. websocket-spec
  2. WEBSOCKET_SPEC-27

Clean up specifiction of allowable parameters on @WebSocketMessage methods

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None

      Description

      Section 4.3.3

      • Why does the entity have to come in the first parameter? Can't we just say the first (and only) parameter that is not of type Session and isn't annotated with @WebSocketPathParam annotation?
      • Why can't the entity param be of any type? Otherwise decoders are never utilized.

      Also, @WebSocketMessage javadoc.

        Activity

        dannycoward created issue -
        Hide
        dannycoward added a comment -

        Specifically: allow all types for which there are decoders to be allowed here, and also the async callbacks.

        Show
        dannycoward added a comment - Specifically: allow all types for which there are decoders to be allowed here, and also the async callbacks.
        Hide
        dannycoward added a comment -

        fixed per comment in upcoming v009

        Show
        dannycoward added a comment - fixed per comment in upcoming v009
        dannycoward made changes -
        Field Original Value New Value
        Status Open [ 1 ] Resolved [ 5 ]
        Tags v009
        Resolution Fixed [ 1 ]

          People

          • Assignee:
            Unassigned
            Reporter:
            dannycoward
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: