base on TCP/HTTP/UDP/QUIC client/server with Reactor over Netty # Reactor Netty [![Join the chat at https://gitter.im/reactor/reactor-netty](https://img.shields.io/gitter/room/nwjs/nw.js.svg)](https://gitter.im/reactor/reactor-netty) [![Reactor Netty](https://img.shields.io/maven-central/v/io.projectreactor.netty/reactor-netty.svg?colorB=brightgreen)](https://mvnrepository.com/artifact/io.projectreactor.netty/reactor-netty) [![publish](https://github.com/reactor/reactor-netty/actions/workflows/publish.yml/badge.svg)](https://github.com/reactor/reactor-netty/actions/workflows/publish.yml) [![CodeQL](https://github.com/reactor/reactor-netty/actions/workflows/codeql-analysis.yml/badge.svg)](https://github.com/reactor/reactor-netty/actions/workflows/codeql-analysis.yml) `Reactor Netty` offers non-blocking and backpressure-ready `TCP`/`HTTP`/`UDP`/`QUIC` clients & servers based on `Netty` framework. ## Getting it `Reactor Netty` requires Java 8 or + to run. With `Gradle` from [repo.spring.io](https://repo.spring.io) or `Maven Central` repositories (stable releases only): ```groovy repositories { //maven { url 'https://repo.spring.io/snapshot' } mavenCentral() } dependencies { //compile "io.projectreactor.netty:reactor-netty-core:1.3.2-SNAPSHOT" compile "io.projectreactor.netty:reactor-netty-core:1.3.1" //compile "io.projectreactor.netty:reactor-netty-http:1.3.2-SNAPSHOT" compile "io.projectreactor.netty:reactor-netty-http:1.3.1" } ``` See the [Reference documentation](https://projectreactor.io/docs/netty/release/reference/index.html#getting) for more information on getting it (eg. using `Maven`, or on how to get milestones and snapshots). ## Getting Started New to `Reactor Netty`? Check this [Reactor Netty Workshop](https://violetagg.github.io/reactor-netty-workshop/) and the [Reference documentation](https://projectreactor.io/docs/netty/release/reference/index.html) Here is a very simple `HTTP` server and the corresponding `HTTP` client example ```java HttpServer.create() // Prepares an HTTP server ready for configuration .port(0) // Configures the port number as zero, this will let the system pick up // an ephemeral port when binding the server .route(routes -> // The server will respond only on POST requests // where the path starts with /test and then there is path parameter routes.post("/test/{param}", (request, response) -> response.sendString(request.receive() .asString() .map(s -> s + ' ' + request.param("param") + '!') .log("http-server")))) .bindNow(); // Starts the server in a blocking fashion, and waits for it to finish its initialization ``` ```java HttpClient.create() // Prepares an HTTP client ready for configuration .port(server.port()) // Obtains the server's port and provides it as a port to which this // client should connect .post() // Specifies that POST method will be used .uri("/test/World") // Specifies the path .send(ByteBufFlux.fromString(Flux.just("Hello"))) // Sends the request body .responseContent() // Receives the response body .aggregate() .asString() .log("http-client") .block(); ``` ## Getting help Having trouble with `Reactor Netty`? We'd like to help! * If you are upgrading, read the [release notes](https://github.com/reactor/reactor-netty/releases) for upgrade instructions and *new and noteworthy* features. * Ask a question - we monitor [stackoverflow.com](https://stackoverflow.com) for questions tagged with [`reactor-netty`](https://stackoverflow.com/questions/tagged/reactor-netty). You can also chat with the community on [Gitter](https://gitter.im/reactor/reactor-netty). * Report bugs with `Reactor Netty` at [github.com/reactor/reactor-netty/issues](https://github.com/reactor/reactor-netty/issues). * More about [Support and Deprecation policies](https://github.com/reactor/.github/blob/main/SUPPORT.adoc) ## Reporting Issues `Reactor Netty` uses `GitHub’s` integrated issue tracking system to record bugs and feature requests. If you want to raise an issue, please follow the recommendations below: * Before you log a bug, please [search the issue tracker](https://github.com/reactor/reactor-netty/search?type=Issues) to see if someone has already reported the problem. * If the issue doesn't already exist, [create a new issue](https://github.com/reactor/reactor-netty/issues/new/choose). * Please provide as much information as possible with the issue report, we like to know the version of `Reactor Netty` that you are using, as well as your `Operating System` and `JVM` version. * If you want to raise a security vulnerability, please review our [Security Policy](https://github.com/reactor/reactor-netty/security/policy) for more details. ## Contributing See our [Contributing Guide](https://github.com/reactor/.github/blob/main/CONTRIBUTING.md) for information about contributing to `Reactor Netty`. ## Building from Source You don't need to build from source to use `Reactor Netty` (binaries in [repo.spring.io](https://repo.spring.io)), but if you want to try out the latest and greatest, `Reactor Netty` can be easily built with the [gradle wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html). You also need JDK 1.8. ```shell $ git clone https://github.com/reactor/reactor-netty.git $ cd reactor-netty $ ./gradlew build ``` If you want to publish the artifacts to your local `Maven` repository use: ```shell $ ./gradlew publishToMavenLocal ``` ## Javadoc https://projectreactor.io/docs/netty/release/api/ ## Guides * https://projectreactor.io/docs/netty/release/reference/index.html * https://violetagg.github.io/reactor-netty-workshop/ ## License `Reactor Netty` is Open Source Software released under the [Apache License 2.0](https://www.apache.org/licenses/LICENSE-2.0) ", Assign "at most 3 tags" to the expected json: {"id":"8485","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"