4.x - Add ability to configure routing for an existing socket

[romain-grecourt]

In 3.x users could define "named" sockets in configuration and set-up routing for those sockets programmatically.

In the current 4.x state (at least in 4.0.0-RC1), the only way to set-up routing for a socket is when creating the socket via the putSocket method on the server builder.

The workaround to emulate the 3.x use-case is to re-create the socket:

.putSocket("admin", socket -> socket.from(server.sockets().get("admin"))
                        .routing(Main::adminSocket))

---

Side by side comparison

Given the following application.yaml:

server:
  port: 8080
  host: "localhost"
  sockets:
    - name: "admin"
      port: 8081

In 3.x:

WebServer.builder(createPublicRouting())
    .config(config.get("server"))
    .addNamedRouting("admin", Routing.builder()
    .get("/admin", (req, res) -> res.send("Hello Admin!!"))
    .build())

In 4.x:

WebServer.builder()
        .config(config.get("server"))
        .update(builder -> builder
                .putSocket("admin", socket -> socket.from(builder.sockets().get("admin"))
                        .routing(routing -> routing.get("/admin", (req, res) -> res.send("Hello Admin!!")))))
        .build()