websocket-spec
  1. websocket-spec
  2. WEBSOCKET_SPEC-38

Clarify error conditions on connections in the API

    Details

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

      Description

      In particular, the different categories of error conditions and where they are handler (container/application).

      Also, why is EncodeException a checked exception instead of a runtime one ?

        Activity

        Hide
        dannycoward added a comment -

        all categories are now clarified in the spec.

        Decode exceptions are checked to allow explicit handing of malformed messages. Websocket endpoints can typically survive such cases, and using the onError mechanism, its likely that the websocket can still do something useful with the raw message even when the decoder has a problem.

        Show
        dannycoward added a comment - all categories are now clarified in the spec. Decode exceptions are checked to allow explicit handing of malformed messages. Websocket endpoints can typically survive such cases, and using the onError mechanism, its likely that the websocket can still do something useful with the raw message even when the decoder has a problem.

          People

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

            Dates

            • Created:
              Updated:
              Resolved: