Well…
it appears that the java xmlrpc client and the urscript client share some resources.
its a python server. we hadnt set any custom timeout, but after adding this line:
socket.setConnectionTimeout(0.1)
everything runs snappy with no delay. afaik - you could set it to whatever you want. We think this is an OK solution; doesnt quite feel like a hack, but also cant help but think this is really a client-side mis-behavior.
The only way reducing the connection timeout to near-zero on the server side could “fix” it is if the both the java client and urscript client share the same socket. Otherwise (ie - outside of polyscope) the server has no problem handling multiple clients and the effect of server-side connection timeout is not felt.