https://issues.apache.org/bugzilla/show_bug.cgi?id=56026
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #1 from Mark Thomas <ma...@apache.org> ---
I have some sympathy with this view. Given that the Javadoc for
RemoteEndpoint.Basic explicitly states that concurrent attempts to send
messages are not allowed and the Javadoc for RemoteEndpoint.Async doesn't,
you'd be forgiven for thinking that meant that RemoteEndpoint.Async permitted
concurrent attempts to send messages.
Unfortunately, the (not very well documented) intention of the WebSocket EG was
not to allow concurrent attempts to send messages. [1]
I did take a quick look at adding an option to relax (i.e. ignoring) this but
the change required to do this with the current Tomcat code would be far from
trivial.
I'm marking this as INVALID since the intention of the EG was to not allow this
but WONTFIX is almost as appropriate if this is viewed as an enhancement
request.
As an aside, one reason not to implement this particular enhancement is that
apps that depended on it would not be portable between containers.
[1]
https://java.net/projects/websocket-spec/lists/jsr356-experts/archive/2013-02/message/1
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
