From: Danny Coward <danny.coward_at_oracle.com>
Date: Fri, 22 Feb 2013 17:41:37 -0800

Hello experts,

I have posted an updated v013 of the specification in the usual place:-

http://java.net/projects/websocket-spec/downloads/directory/Spec%20javadoc%20Drafts/v013

and the API workspace is tagged: tags/javax.websocket-api-1.0-b13

At the bottom I have included a diff of the JIRA issues since v013. In
particular, this includes the annotation renames and RemoteEndpoint
refactorization.

It does not include the largest remaining issue we have: the
non-scan/programmatic deployment usecase which we have been talking
about this week. I'd like to think a bit more about it over the weekend,
but do expect more on that next week. I think we can address it; the
question in my mind is what the best way to do it.

We've got through an enormous number of issues since Public Draft:
thankyou for all your many contributions !

My plan is to close out the remaining JIRA issues, and anything else
left over on the mailing list next week, and to publish a v014 draft
next Friday. If all the issues are resolved, I'd like to submit this to
the JCP as the proposed final draft.

Thanks,

- Danny

WEBSOCKET_SPEC-82 <http://java.net/jira/browse/WEBSOCKET_SPEC-82>
@WebSocketEndpoint's configuration attribute
<http://java.net/jira/browse/WEBSOCKET_SPEC-82>
WEBSOCKET_SPEC-132 <http://java.net/jira/browse/WEBSOCKET_SPEC-132>
RemoteEndpoint#setBatchingAllowed(boolean) should throw IOException
<http://java.net/jira/browse/WEBSOCKET_SPEC-132>
WEBSOCKET_SPEC-139 <http://java.net/jira/browse/WEBSOCKET_SPEC-139>
getNegotiatedSubprotocol(): not sure if we can return null
<http://java.net/jira/browse/WEBSOCKET_SPEC-139>
WEBSOCKET_SPEC-138 <http://java.net/jira/browse/WEBSOCKET_SPEC-138>
websockets api javadoc: include message handler registration for onOpen
method <http://java.net/jira/browse/WEBSOCKET_SPEC-138>
WEBSOCKET_SPEC-69 <http://java.net/jira/browse/WEBSOCKET_SPEC-69>
Publish same programmatic endpoint type to many different paths
<http://java.net/jira/browse/WEBSOCKET_SPEC-69>
WEBSOCKET_SPEC-98 <http://java.net/jira/browse/WEBSOCKET_SPEC-98>
Consider a property bag on EndpointConfiguration instead of subclassing
for shared application state
<http://java.net/jira/browse/WEBSOCKET_SPEC-98>
WEBSOCKET_SPEC-126 <http://java.net/jira/browse/WEBSOCKET_SPEC-126>
ServerEndpointConfiguration.matchesURI
<http://java.net/jira/browse/WEBSOCKET_SPEC-126>
WEBSOCKET_SPEC-128 <http://java.net/jira/browse/WEBSOCKET_SPEC-128>
DefaultServerConfiguration - methods implementation - b12
<http://java.net/jira/browse/WEBSOCKET_SPEC-128>
WEBSOCKET_SPEC-140 <http://java.net/jira/browse/WEBSOCKET_SPEC-140>
Clarify relationship between
WebSocketContainer#setMaxSessionIdleTimeout() and Session#setTimeout()
<http://java.net/jira/browse/WEBSOCKET_SPEC-140>
WEBSOCKET_SPEC-133 <http://java.net/jira/browse/WEBSOCKET_SPEC-133>
DefaultServerConfiguration#getEndpointClass() should return Class<?
extends Endpoint> <http://java.net/jira/browse/WEBSOCKET_SPEC-133>
WEBSOCKET_SPEC-141 <http://java.net/jira/browse/WEBSOCKET_SPEC-141>
websockets api: how to pass instance to ServerEndPointConfiguration ?
<http://java.net/jira/browse/WEBSOCKET_SPEC-141>
WEBSOCKET_SPEC-103 <http://java.net/jira/browse/WEBSOCKET_SPEC-103>
DefaultServerConfiguration used in @WebSocketEndpoint
<http://java.net/jira/browse/WEBSOCKET_SPEC-103>
WEBSOCKET_SPEC-144 <http://java.net/jira/browse/WEBSOCKET_SPEC-144>
Discrepancy between URIs of programmatic and annotated endpoint
<http://java.net/jira/browse/WEBSOCKET_SPEC-144>
WEBSOCKET_SPEC-147 <http://java.net/jira/browse/WEBSOCKET_SPEC-147>
@WebSocketClose: javadoc not in sync with the Java API Web Socket pdf
document <http://java.net/jira/browse/WEBSOCKET_SPEC-147>
WEBSOCKET_SPEC-145 <http://java.net/jira/browse/WEBSOCKET_SPEC-145>
Rename HandshakeRequest.getSession -> getHttpSession
<http://java.net/jira/browse/WEBSOCKET_SPEC-145>
WEBSOCKET_SPEC-143 <http://java.net/jira/browse/WEBSOCKET_SPEC-143>
ContainerProvider javadoc need to update the location of service
provider <http://java.net/jira/browse/WEBSOCKET_SPEC-143>
WEBSOCKET_SPEC-131 <http://java.net/jira/browse/WEBSOCKET_SPEC-131>
Consider merging RemoteEndpoint and Session
<http://java.net/jira/browse/WEBSOCKET_SPEC-131>
WEBSOCKET_SPEC-134 <http://java.net/jira/browse/WEBSOCKET_SPEC-134>
ContainerProvider#getWebSocketContainer()
<http://java.net/jira/browse/WEBSOCKET_SPEC-134>
WEBSOCKET_SPEC-88 <http://java.net/jira/browse/WEBSOCKET_SPEC-88>
CloseReason changes <http://java.net/jira/browse/WEBSOCKET_SPEC-88>
WEBSOCKET_SPEC-136 <http://java.net/jira/browse/WEBSOCKET_SPEC-136>
Session.getRequestURI() . includes the query string ?
<http://java.net/jira/browse/WEBSOCKET_SPEC-136>
WEBSOCKET_SPEC-111 <http://java.net/jira/browse/WEBSOCKET_SPEC-111>
Missing WebSocketClient#configuration attribute
<http://java.net/jira/browse/WEBSOCKET_SPEC-111>
WEBSOCKET_SPEC-118 <http://java.net/jira/browse/WEBSOCKET_SPEC-118>
Scanning scheme forces creation of ServerEndpoinConfiguration class even
for vanilla endpoints <http://java.net/jira/browse/WEBSOCKET_SPEC-118>
WEBSOCKET_SPEC-97 <http://java.net/jira/browse/WEBSOCKET_SPEC-97>
Consider using jax-rs MultiValueMap to represent Http headers in the
handshake request and response
<http://java.net/jira/browse/WEBSOCKET_SPEC-97>
WEBSOCKET_SPEC-137 <http://java.net/jira/browse/WEBSOCKET_SPEC-137> An
incoming message that is too big: should it cause the connection to
close ? Or should the implementation report the error to the endpoint
and move on ? <http://java.net/jira/browse/WEBSOCKET_SPEC-137>
WEBSOCKET_SPEC-110 <http://java.net/jira/browse/WEBSOCKET_SPEC-110>
Rename SendHandler#setResult
<http://java.net/jira/browse/WEBSOCKET_SPEC-110>
WEBSOCKET_SPEC-9 <http://java.net/jira/browse/WEBSOCKET_SPEC-9> API
Usability: Consider API renaming, minor refactorizations for usability
<http://java.net/jira/browse/WEBSOCKET_SPEC-9>

-- 
<http://www.oracle.com> 	*Danny Coward *
Java EE
Oracle Corporation