websocket-spec
  1. websocket-spec
  2. WEBSOCKET_SPEC-96

Allow Java primitives and boxed equivalents as message parameters to @WebSocketMessage methods

    Details

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

      Description

      I think this can be unambiguously defined for incoming string messages. For each of the Java primitives, use the string constructor of the boxed equivalent using the incoming string parameter, and unbox it. For the boxed primitives, use the string constructor.

      For binary messages, I don't think there's a standard way.

        Activity

        Hide
        dannycoward added a comment -

        will propose text message -> primitive/boxed equivalents decoders / i.e. should be able to have them as method parameters on @WebSocketMessage

        Show
        dannycoward added a comment - will propose text message -> primitive/boxed equivalents decoders / i.e. should be able to have them as method parameters on @WebSocketMessage
        Hide
        dannycoward added a comment -

        I have updated the spec and javadoc for this.

        Show
        dannycoward added a comment - I have updated the spec and javadoc for this.

          People

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

            Dates

            • Due:
              Created:
              Updated:
              Resolved: