Issue Details (XML | Word | Printable)

Key: WEBSOCKET_SPEC-168
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: dannycoward
Reporter: mikc22
Votes: 0
Watchers: 0
Operations

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

websockets api: improve maxMessage description

Created: 11/Mar/13 01:10 PM   Updated: 19/Mar/13 06:40 PM   Resolved: 19/Mar/13 06:40 PM
Component/s: None
Affects Version/s: 1.0
Fix Version/s: None

Time Tracking:
Not Specified

Tags: final
Participants: dannycoward and mikc22


 Description  « Hide

The current maxMessageSize annotation javadoc doesn't say when we can use this annotation and what is the behaviour on specified endpoints. E.g. can I supply maxMessageSize for stream as well ?



dannycoward added a comment - 11/Mar/13 11:30 PM

this should correspond to the semantics of the session.getMaxTextMessageBufferSize().


dannycoward added a comment - 19/Mar/13 06:40 PM

I read back the original request. For this version, the attribute only applies when annotating methods that take the whole message, not for partial message processing handlers or those using Readers or InputStreams. The javadoc has been appropriately updated.


dannycoward made changes - 19/Mar/13 06:40 PM
Field Original Value New Value
Status Open [ 1 ] Resolved [ 5 ]
Assignee dannycoward [ dannycoward ]
Tags final
Resolution Fixed [ 1 ]