websocket-spec
  1. websocket-spec
  2. WEBSOCKET_SPEC-29

Clarify certain lifecycle cases onOpen/onClose/onError

    Details

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

      Description

      In particular:

      • Seems the following sentence: "The container may not invoke the close method on an endpoint
        until the open method has either completed, or the container has determined that it will
        not wait until it has completed and has removed it from service [WSC-39]."
        implies/could be rephrased to "The container may or may not wait until the onOpen method completes before calling onClose."
        Is that the intended implication?
        How about onError? Is it called before onClose? May onClose be called before onError completes? May onError be called before onOpen completes? Am I not guaranteed to get onOpen, onError and onClose calls for one single session on the same thread?

        Activity

        dannycoward created issue -
        Hide
        dannycoward added a comment -

        This has been simplified in version 008.

        Show
        dannycoward added a comment - This has been simplified in version 008.
        Hide
        dannycoward added a comment -

        This rather confusing piece is clarified in the specification v008.

        Show
        dannycoward added a comment - This rather confusing piece is clarified in the specification v008.
        dannycoward made changes -
        Field Original Value New Value
        Status Open [ 1 ] Resolved [ 5 ]
        Tags v008
        Resolution Fixed [ 1 ]

          People

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

            Dates

            • Created:
              Updated:
              Resolved: