Provide advice on number of instances and connections for WebSocketGraphQlClient and RSocketGraphQlClient

[viral-kondhia]

Please add sample application for WebSocketGraphQlClient which uses ReactorNettyWebSocketClient
https://github.com/spring-projects/spring-graphql/tree/main/samples/webflux-websocket this uses GraphqlTester API for client which does not demonstrate actual usage of WebSocketGraphQlClient with ReactorNettyWebSocketClient

[rstoyanchev]

We have plans to replace the samples, see #208. You could leave a comment there, but generally, the client and tester APIs are pretty well aligned. They should feel the same to create and execute a request. There is also the reference docs.

[viral-kondhia]

Documentation does not tells how to execute the request its only constructing the object for client.
Also more details will be helpful as websocket might require explicit closing and start of tcp
Whether WebSocketGraphQlClient should be singleton or it can be created for each request ?
Also see #369 #369

[rstoyanchev]

Regarding lifecycle questions, most likely you'll want a singleton assuming you want to have one, shared (multiplexed) connection at a time. There are methods for start and stop, and the Javadoc should help to fill in a few of these blanks, but overall, we can use this as an opportunity to improve the reference documentation.

As for executing requests, there is a section focusing on requests, which is independent of how the client was created. Could you take a look and see if anything is missing from your perspective?