https://issues.apache.org/bugzilla/show_bug.cgi?id=56026
Simone Bordet <simone.bor...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |---
--- Comment #2 from Simone Bordet <simone.bor...@gmail.com> ---
Mark, thanks for your comments.
I am frankly surprised that an expert group states that:
"[async writes] should not be permitted and an IllegalStateException be thrown.
My reasoning for this is that was allowed it would open up all sorts of
buffering requirements for the container that could get tricky to manage."
Now those sorts of tricky buffering requirements must be managed by the
application, with almost 100% chance that average joe websocket get them wrong.
For a simple chat application, an application developer must manage the
buffering and possibly stack overflows due to callback invocations.
Containers should solve those problems on behalf of the application writers,
otherwise one could say that transaction management or ORM mapping are too
tricky to manage and better left to JEE application writers.
I hope you can change your mind on this issue :)
I see this problem as a lack of detail in the specification rather than a real
intent to put burden onto application developer's shoulders.
Thanks!
--
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
