I am conducting test of the use of Magma with one server and one client in two separate places in the Internet (France<-->Taiwan link), throught not so fast link. So far so good, and as wrote Göran, Index are very helpful.
From time to time I got some error message like this one in the server:
dataHandler: selected socket fd=45 flags=0x2 would block (why?)
Then a MaNetworkError 'Connection closed while waiting for response.' in the client side.
The situation is a bit special: To reduce the latency from the client side, I fork the commits in separate processes.
Looking at the process browser, I can see that Magma does it job to queue the commit (I guess it is what is about Semaphore use).
Could the problem be related to the use of only one session for several forked commit?
Hilaire