netty

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

Not that complicated to implement:

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

A failed HttpResponse can be converted into a normal HttpResponse using HttpResponse.recover(...).
For example:

HttpResponse failed = HttpResponse.ofFailure(new IllegalArgumentException("..."));
failed.recover(cause -> {
   if (cause instanceof IllegalArgumentException) {
       return HttpResponse.of(HttpStatus.BAD_REQUEST);
   }

   if (cause instanceof IllegalStateExcepti

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

Demonstrate how MultiAddressHttpClientBuilder.SingleAddressInitializer can be used to configure underlying clients based on host and port.

An example can be based on one of the http/helloworld examples. Not necessary to repeat all 4 API variants. The goal is only to demonstrate builder features. For example,

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