Hi Ravichandran, Your, design is really cool and I like the way you have designed the core and the transport modules. Few suggestions and comments are
1. You have included a connector resolver and a metadata collector resolver in the core module design. What is the behavior of Resolver? Does it support dynamic transport registration? E.g Whether we can register a transport in a configuration file or some location that core module will automatically pick up and register it with Agent without external changes at core modules. 2. There can be different types of Receivers. E.g One Receiver would be SFTP Listener listening on a particular port, and another one would be a connector to SCP location that pulls data. How does the core interface support both types of transports? 3. How does the thread model design look like?. E.g for passthrough scenarios where messages are directly transferred from receiver to sender vs involving intermediate mediation. 4. Is there any plan on connection pooling implementation on the sender side. thanks Isuru On Thu, Apr 30, 2020 at 7:21 PM Ravichandran, Sharanya <[email protected]> wrote: > Hi , > > > We have added the details about how to introduce a new transport to MFT in > the below mentioned document.[1] > > > Please take a look and provide feedback. > > > [1] > https://docs.google.com/document/d/17AlwsQwXvBUBPt__xexqKLoPdhGEGcG0EgLPZ22nTTQ/edit?usp=sharing > > > > Thanks, > > Sharanya R. > -- Research Software Engineer Indiana University, IN
