Erlang general question on socket?

Yes. The rpc module even has multicall which takes a list of nodes and will do exactly what you described. It won't hold your sockets open when it's not using them either.

Yes. The rpc module even has multicall, which takes a list of nodes and will do exactly what you described. It won't hold your sockets open when it's not using them either.

Despite what the other answers say, Erlang's default behavior does not satisfy your constraints. A typical network of Erlang nodes using Erlang distribution will remain densely connected (every node connected to every other node) with TCP sockets open even when you're not using them. You will either have to use -connect_all false and manage opening/closing the connections to other nodes yourself, or you will have to develop your own distribution protocol.

I would recommend the latter, especially since you are learning. The trick to make it easy is to use term_to_binary and binary_to_term.

Afaik -Connect_all false just prevents that a node connects to all nodes when joining a network. A once opened connection is still keept open 'forever'. – ZeissS Nov 17 '10 at 9:30 Of course, doing -connect_all false does not solve the problem by itself.

You must also use net_kernel:connect_node/1 and erlang:disconnect_node/1 strategically. This is what I meant by "manage opening/closing the connections to other nodes yourself". – YOUR ARGUMENT IS VALID Nov 17 '10 at 10:08.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.