Issue Details (XML | Word | Printable)

Key: WEBSOCKET_SPEC-80
Type: New Feature New Feature
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: dannycoward
Reporter: dannycoward
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
websocket-spec

Semantics of undeploy of a websocket

Created: 21/Dec/12 11:38 PM   Updated: 05/Feb/13 12:04 AM  Due: 08/Feb/13   Resolved: 05/Feb/13 12:04 AM
Component/s: None
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Tags: v012
Participants: dannycoward


 Description  « Hide

Should containers call onClose() if they decide to close the connection? (in the absence of a close frame) Or should the developer use some other lifecycle to know the container is closing the connection.
Is the container/sys admin allowed to undeploy an endpoint if an endpont is being badly behaved - e.g. throwing runtime exceptions every time its called.



dannycoward added a comment - 03/Feb/13 09:47 PM

We've decided onClose() is called whether the local container closes it or the remote peer sends the close frame.

Awaiting more info on the undeploy situation from the reporter.


dannycoward added a comment - 05/Feb/13 12:04 AM

On undeploy, we are not specifying this process for this version. So the specification doesn't need to say anything around the reasoning or circumstances of undeploying applications.


dannycoward added a comment - 05/Feb/13 12:04 AM

This is now resolved.