Libfabric transport layer support

[xendo]

In your roadmap i can see that you plan to add additional transport layers for the transfer engine. I was wondering if you also considered adding support for libfabric: https://github.com/ofiwg/libfabric . That would give you support for several providers at a single try.

Is there anything I should be aware of before trying to implement and contribute such support?

P.S.
I really enjoyed reading through your documentation, really high quality stuff

[alogfans]

As we have refactored the code recently, adding a new transport will be more easier. We appreicate the community to submit additional transports.

In my opinion, things to be aware before coding:

• Current transfer API is one-sided. Though it is technically possible to extend it to support two-sided (send/recv) operations, we prefer to find approaches to make one-sided operations more efficient.
• Most transport needs to manage metdata (e.g. segment info) by it self. You can refer to tcp transport at the beginning.