That is shocking and disturbing!
Many projects do not have access to the TCK (license incompatibility with
open source projects).
Having that much change would indicate that this either isn't a minor point
release, or the spec was inadequate and is being tightened up.
It would be one thing, if the open questions on the WEBSOCKET_SPEC jira had
been answered, but there are still many that haven't even had a response
yet.
How about another spec pdf with all of the changes?
Or a version 1.1.1 javadoc update with all of the behavioral changes?
Or answers to the open questions on the spec jira?
--
Joakim Erdfelt <joakim_at_intalio.com>
webtide.com <http://www.webtide.com/> - intalio.com/jetty
Expert advice, services and support from from the Jetty & CometD experts
eclipse.org/jetty - cometd.org
On Wed, Oct 8, 2014 at 1:11 PM, Kevin Sutter <sutter_at_us.ibm.com> wrote:
> Hi,
> My normal conduit for the WebSocket expert group is not at work this week,
> so I thought I would try this route to get a quicker answer... We're
> looking to update our WebSocket 1.0 implementation to satisfy the new
> methods introduced by WebSocket 1.1. No big deal with that piece. But, we
> were very surprised by the number of tests that the TCK increased by.
>
> For WebSocket 1.0, there were 262 tests. According to the readme for the
> 1.1 TCK, there are now 664 tests! Really? An increase of 400 tests for a
> minor update?
>
> Can somebody help explain this? Or, are we interpreting something
> incorrectly?
>
> Thank you for any insights!
> Kevin
>
>
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------
> Kevin Sutter
> STSM, Java EE and Java Persistence API (JPA) architect
> mail: sutter_at_us.ibm.com, Kevin Sutter/Rochester/IBM
> http://webspherepersistence.blogspot.com/
> phone: tl-553-3620 (office), 507-253-3620 (office)
> http://openjpa.apache.org/
>