Am 2020-04-15 um 23:05 schrieb r...@apache.org:
This is an automated email from the ASF dual-hosted git repository.
remm pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tomcat.git
The following commit(s) were added to refs/heads/master by this push:
new 92923fe Proposed Connector API and XML refactoring
92923fe is described below
commit 92923febadb5d7901747530272302dc3da6311c2
Author: remm <r...@apache.org>
AuthorDate: Wed Apr 15 23:04:47 2020 +0200
Proposed Connector API and XML refactoring
See https://cwiki.apache.org/confluence/display/TOMCAT/Connector+API+refactoring
To add some fuel to the fire: This looks like a start.
I always liked the approach HTTPd took, addd a Listen <IP>:<Port> +
VirtualHost <IP>:<Port>.
Even in the new proposal you have redundancies: scheme, secure,
SSLEnabled. Why can't the endpoint or rather a class using this endpoint
decide what protocol it speaks when TLS config is nested?
What I never understood with Tomcat why Host configs applies to *all*
connectors. I cannot freely apply hosts to IP/port combos and selecting
on a host level what type of protocol I want to have.
My understanding is:
* An endpoint impl is a pure socket which can run any protocol
* A protocol is uses an endpoint
* A Host declares to use a specific endpoint/protocol
* Either proto or host declare TLS
Which such decoupling one could even introduce AJPS.
But a guess this is a lot of work to do.
M
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
