Issue Details (XML | Word | Printable)

Key: WEBSOCKET_SPEC-79
Type: New Feature New Feature
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: dannycoward
Reporter: dannycoward
Votes: 0
Watchers: 1
Operations

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

Deployment on the server by instance

Created: 21/Dec/12 11:36 PM   Updated: 28/Feb/13 08:45 PM  Due: 08/Feb/13   Resolved: 28/Feb/13 08:45 PM
Component/s: None
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Issue Links:
Related
 

Tags: v014
Participants: dannycoward


 Description  « Hide

ALlow developers to create their own instances of websocket endpoints and deploy them (singletons)



dannycoward added a comment - 17/Jan/13 12:55 AM

Also, as Rossen points out, the ServletContext in Servlet 3.0 allows registration of Servlets and Filters by instance and by type.

Note: the 'default' mode for server websockets is to use a new instance per client connection. So will the singleton model be ok for the deploy-by-instance case ?


dannycoward added a comment - 28/Feb/13 01:32 AM

eg seems to be ok with add getEndpointInstance() to ServerEndpointConfig.Configurator which will address this.


dannycoward added a comment - 28/Feb/13 08:45 PM

v014 allows the developer to control the instance creation of endpoints using the

ServerEndpointConfig.Configurator.getEndpointInstance(Class<T> endpointClass) call.