Issue Details (XML | Word | Printable)

Key: WEBSOCKET_SPEC-150
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Fixed
Priority: Minor Minor
Assignee: dannycoward
Reporter: dannycoward
Votes: 0
Watchers: 0
Operations

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

Encoder/Decoder lifecycle consistency between pe and ae's

Created: 23/Feb/13 12:41 AM   Updated: 28/Feb/13 09:42 PM   Resolved: 28/Feb/13 09:13 PM
Component/s: None
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Tags: v014
Participants: dannycoward and jitu


 Description  « Hide

Currently, Encoders and Decoders are singletons for programmatic endpoints

and they are per-connection objects for annotated endpoints.

They should have the same lifecycle.

Probably per-connection is best, so register by class on EndpointConfiguration, not by instance.

Also, they need some view into the rest of the websocket API. Suggest

setEndpointConfiguration(EndpointConfiguration ec)

as a mini lifecycle.



No work has yet been logged on this issue.