Parent Directory | Revision Log
Sticky Revision: |
When using Servlet 3.1 non-blocking reads with an AJP connector, make the reads between the AJP body messages from the server non-blocking. Once any part of a message is read, the remainder of the message will be read using blocking IO.
More side-effects from making endpoints generic
Pull up SocketWrapper
No need to use fully-qualified name now that it has been renamed from ProtocolHandler (that clashed with an internal Tomcat class)
Refactor to simplify support for non-blocking IO across all HTTP connectors
Rename ProtocolHandler to HttpUpgradeHandler
upgradeDispatch() needs socket status to differentiate between read and write
Switch the Processors to use the Servlet 3.1 upgrade objects - Upgrade process still broken
Code clean-up - Java 7 <> - UCDetector use of final - Make use of unused fields where appropriate
Refactor the connectors to allow lighter weight UpgradeProcessor implementations that do not depend on Http11Processors. The main change is the expansion of the Processor interface and the use of that interface rather than the AbstractProcessor.
Use a lighter weight processor for upgrades. Note that extending the Http11 processors is a hack that I think can be removed with some further refactoring of the connectors.
Initial web socket implementation with example. See code for TODOs.
Whitespace removal from /java/org/apache/coyote
Pull up Handler.process
Pull up common code
Pull up more common code in Processor constructors
Pull up common endpoint code in Processor constructors
Pull up the request and response objects since they are common between AJP and HTTP
Pull up common getExecutor code
Create an AbstractProcessor. Start to pull common code from AJP and HTTP processors to this abstract class.
This form allows you to request diffs between any two revisions of this file. For each of the two "sides" of the diff, enter a numeric revision.
infrastructure at apache.org | ViewVC Help |
Powered by ViewVC 1.1.26 |