[WEBSOCKET_SPEC-29] Clarify certain lifecycle cases onOpen/onClose/onError Created: 12/Oct/12  Updated: 17/Nov/12  Resolved: 17/Nov/12

Status: Resolved
Project: websocket-spec
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: dannycoward Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: v008


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?

Comment by dannycoward [ 17/Nov/12 ]

This has been simplified in version 008.

Comment by dannycoward [ 17/Nov/12 ]

This rather confusing piece is clarified in the specification v008.

Generated at Sun Feb 19 12:10:04 UTC 2017 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.