netty

这里的路由和server通信是否可以用一个长连接来维护更好

Not that complicated to implement:

• introduce in SslClientContext the same kind of changes as in SslServerContext so it's no longer

AnnotatedServiceBindingBuilder and VirtualHostAnnotatedServiceBindingBuilder currently don't share a common interface for its methods, such as pathPrefix() and exceptionHandlers(). This means, a contributor can add a builder method to one builder but not to the other by mistake. By making both builder extend a new interface AnnotatedServiceConfigSetters, we could prevent such a mistake.

Motivation

I recently ran into an issue where an exception thrown in Micrometer caused my request to break. The actual issue I ran into is not in reactor although reactor was used. However as reactor uses Micrometer as well and e.g. [here|https://github.com/reactor/reactor-netty/blob/main/reactor-netty-core/src/main/java/reactor/netty/channel/AbstractChannelMetricsHandler.java] there also does

There are many links to external documentation and specifications contained in the ServiceTalk source code. Many of these links are currently http links where they could be https links. For example, all links to http://reactivex.io/documentation could be upgraded to https.

Converting all existing http links to https within the ServiceTalk source will require checking to ensure that

If you r going to wait response,or block the goroutine in a getty session(tcp conection), task pool can not be null。

func (s *Server) newSession(session getty.Session) error {
	var (
		ok      bool
		tcpConn *net.TCPConn
	)
	
	// 省略部分代码...
	session.SetTaskPool(srvGrpool)
	return nil
}

ortherwise,handleTcpPackage() will blocked,led to the response missing

func (s *session