Allow option to use NIO based SelectChannelConnector for the Jetty Server
-------------------------------------------------------------------------
Key: PAXWEB-101
URL: http://issues.ops4j.org/jira/browse/PAXWEB-101
Project: Pax Web
Issue Type: Improvement
Components: WebContainer
Reporter: Matthew Roy
Assignee: Alin Dreghiciu
Attachments: addNIOpatch.patch
In order to use cometd/bayeux for ajax applications, it is beneficial to use
the NIO based SelectChannelConnector instead of the blocking IO connector for
the Jetty server. I've created a patch that adds a new configuration option
"useNIO", which allows one to specify which type of Connector to create. The
patch also includes a fix which throws a 404 within the ResourceServlet if the
requested resource does not exist. This was based on reading section 102.4 of
the HttpService spec which talks find the resource for an HttpRequest , and
ends by saying "Otherwise the Http Service must return
HttpServletResponse.SC_NOT_FOUND(404) to the client"
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general
