Network Programming: to maintain sockets or not?

Question

I\'m currently translating an API from C# to Java which has a network component.

The C# version seems to keep the input and output streams and the socket open for th

Answer 1

I am coming a bit late, but I didn't see anyone suggest that.

I think it will be wise to consider pooling your connections(doesn't matter if Socket or TCP), being able to maintain couple connections open and quickly reuse them in your code base would be optimal in case of performance.

In fact, Roslyn compiler extensively use this technique in a lot of places. https://github.com/dotnet/roslyn/search?l=C%23&q=pooled&type=&utf8=%E2%9C%93