The request based API allows for custom backends in a way similar to the http package. In order to create a backend you need to implement 4 handler interfaces; one for reading, one for writing, one for misc commands and one for listing files. Each has 1 required method and in each case those methods take the Request as the only parameter and they each return something different. These 4 interfaces are enough to handle all the SFTP traffic in a simplified manner.
The Request structure has 5 public fields which you will deal with.
Below are the methods and a brief description of what they need to do.
Handler for “Get” method and returns an io.Reader for the file which the server then sends to the client.
Handler for “Put” method and returns an io.Writer for the file which the server then writes the uploaded file to. The file opening “pflags” are currently preserved in the Request.Flags field as a 32bit bitmask value. See the SFTP spec for details.
Handles “SetStat”, “Rename”, “Rmdir”, “Mkdir” and “Symlink” methods. Makes the appropriate changes and returns nil for success or an filesystem like error (eg. os.ErrNotExist). The attributes are currently propagated in their raw form (byte) and will need to be unmarshalled to be useful. See the respond method on sshFxpSetstatPacket for example of you might want to do this.
Handles “List”, “Stat”, “Readlink” methods. Gathers/creates FileInfo structs with the data on the files and returns in a list (list of 1 for Stat and Readlink).