On provider side the files should be read from file system (data lake dir), Base64 encoded and sent in payload part of ArtifactResponseMessage. The file name is to be extracted from the ids:target field:
"ids:target" : "http://w3id.org/engrd/connector/artifact/test.txt" -> file name should be test.txt (value after last / )
On consumer side the file should be decoded and saved to file system (data lake dir). The logic should probably be added in ProxyServiceImpl.
Maybe we should consider adding one or two property for enabling/disabling this feature (consumer and provider side).
On provider side the files should be read from file system (data lake dir), Base64 encoded and sent in payload part of ArtifactResponseMessage. The file name is to be extracted from the ids:target field: "ids:target" : "http://w3id.org/engrd/connector/artifact/test.txt" -> file name should be test.txt (value after last / )
On consumer side the file should be decoded and saved to file system (data lake dir). The logic should probably be added in ProxyServiceImpl.
Maybe we should consider adding one or two property for enabling/disabling this feature (consumer and provider side).
You can use branch file_transfer_over_http as a starting point.
Good luck!