[WEBSOCKET_SPEC-38] Clarify error conditions on connections in the API Created: 17/Oct/12 Updated: 14/Dec/12 Resolved: 14/Dec/12
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
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 ?
|Comment by dannycoward [ 14/Dec/12 ]|
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.