Is Service Weaver suitable for writing tcp server？

[wind-c]

I've only seen examples of http.

[rgrandl]

@wind-c it should. E.g., you can run a gRPC server to export the listener instead of a HTTP server. We're working on adding an example to our website.

[wind-c]

@mwhittaker @rgrandl
I wrote the tcp server example and the single-process mode is fine. The new question is, in the multi-process, multi-machine, or multi-replica deployment, how do you find out which replica a given client tcp connection is on? How do you route messages to this tcp connection?

Http is used for request-response services, but for push, notification, chat, pub-sub and other types of services are based on tcp connections, and messages must be routed to the specified client tcp connection.

[wind-c]

The response to the Issue was too slow, and the long wait was too painful.

[rgrandl]

I already answered to this question in the other PR. Can you elaborate on what exactly you're trying to do?

Slowness - we've been a little bit overwhelmed with other things, sorry about that. Open source is just one way we contribute to the project.