You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think a standard usecase for etd is multiple simultaneous transfers. In this case, multiple ports are needed. I think it would be nice to show how to set up say 5 ports available on the etd side.
The text was updated successfully, but these errors were encountered:
For the intended use case - "multiple simultaneous transfers" - you don't need multiple ports! That was the whole point of doing things different (i.e. better) compared to, say, a 2 x jive5ab + m5copy approach.
etd does allow multiple parallel transfers over a single command and single data port, like a proper client/server application should. The multiple data channels are there to simultaneously support different protocols (IPv4 and IPv6, tcp and udt, ...) and/or using specific protocol(s) on specific interfaces and never the amount of parallel transfers.
I think a standard usecase for etd is multiple simultaneous transfers. In this case, multiple ports are needed. I think it would be nice to show how to set up say 5 ports available on the etd side.
The text was updated successfully, but these errors were encountered: