We once tried to merge them, it didn't pan out as we thought. They
eventually drifted apart.
They are probably better left as they are for now. The connectors are
fairly complex and start merging them will almost guaranteed break them.
The NIO connector for example, is spaghetti code heaven, with all kinds
of edge cases, that may seem easy to refactor but are not. but the code
works which is more important than that it looks pretty.
I'm planning on rewriting the NIO connector, but wouldn't dare to do
that in the existing code base, it would take a long time to restabilize
it again, instead I would create a sandbox project, and work on it there.
You can see in trunk, we've already done some refactoring by extracting
thread pooling code into outside classes.
Filip
Kirk True wrote:
Hi all,
There are a number of places in NioEndpoint and JIoEndpoint that share
a good portion of common code. The accessors for common properties
take up a good chunk, but there's also some boilerplate code for
checking if we're paused, running, etc. There are a lot of places
where variable and method scope could be cleaned up too.
Obviously I can't commit this code myself, but if I submitted patches
for it, would they be looked upon favorably or ignored as noise? :)
Thanks,
Kirk
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
