The core documentation on how to make requests says to use xxxNow to make request from a client, but those methods are deprecated, e.g., getNow.

The official Widgets Development Guide only contains the most basic widget types as example.

There is no functional example for a Flot chart in there right now. Or is it?

Since this is one of the most useful and probably used (at leat to me) widgets it would be very helpful to extend that docum

Bug 描述
客户端或服务端发消息,对方收到消息后,没有发送回执,无法判断消息是否发送成功.
这是一个很大的漏洞,如果要做离线消息的话,消息是否发送成功是一个非常重要的点

https://asynchttpclient.github.io/async-http-client/

we don't need a event name.

how to add a global message listener. all event or without event message can send to here.

<img width="287" alt="default" src="https://user-images.githubusercontent.com/2519544/42929452-af25cccc-8b6c-11e8-903d-46fbaaacae1d.png"

In our codebase, we push RequestContext and immediately run some code with try-with-resources.
For example:

try (SafeCloseable ignored = ctx.push()) {
    logger.trace(decorate(msg));
}

If RequestContext provides run(Runnable) or call(Callable) we can reduce boilerplate code and simplify it.

ctx.run(() -> logger.trace(decorate(msg));

This is inspired by g

This should be a really easy one, but I can't seem to find a solution. How do you secure content registered with StaticContentSupport? I'd like to have /protected static content and open static content, with Routing looking something like this:

return Routing.builder()
.register(WebSecurity.create(getSecurity()))
.register("/protected", StaticContentSupport.builder(protectedPath).welcomeFil

There are a number of issues related to LoadBalancedRSocketMono that depend on deeper review of the current implementation:

• #745
• #716
• #713
• #654
• #633
• #725

Please check the reproducible example here: https://github.com/michaelr524/reactor-netty-ssl-leak

mvn clean package
java -jar target/reactor-netty-ssl-leak-1.0-SNAPSHOT.jar 

• Reactor version(s) used: 0.9.4.RELEASE
• Other relevant libraries versions (eg. netty, ...):
• JVM version (javar -version):
  openjdk version "12.0.2" 2019-07-16
  OpenJDK Runtime Environment (build 12.0

It would be nice to have the ability to configure security access for each Kibana space:

• none: no access to one Kibana space
• read: read access to one Kibana space
• all: all access to one Kibana space

All that associated to one role in readonlyrest.yml