c71cbb17d3
Just like with files, the call to the hander to create the Lister is done when the OPENDIR packet is received. This eliminates the need for the lock in the filelist() method and opens the path for eliminating more locks. |
||
|---|---|---|
| examples | ||
| server_standalone | ||
| .gitignore | ||
| .travis.yml | ||
| CONTRIBUTORS | ||
| LICENSE | ||
| README.md | ||
| attrs.go | ||
| attrs_stubs.go | ||
| attrs_test.go | ||
| attrs_unix.go | ||
| client.go | ||
| client_integration_darwin_test.go | ||
| client_integration_linux_test.go | ||
| client_integration_test.go | ||
| client_test.go | ||
| conn.go | ||
| debug.go | ||
| example_test.go | ||
| match.go | ||
| other_test.go | ||
| packet-manager.go | ||
| packet-manager_test.go | ||
| packet-typing.go | ||
| packet.go | ||
| packet_test.go | ||
| release.go | ||
| request-attrs.go | ||
| request-attrs_test.go | ||
| request-errors.go | ||
| request-example.go | ||
| request-interfaces.go | ||
| request-readme.md | ||
| request-server.go | ||
| request-server_test.go | ||
| request-unix.go | ||
| request.go | ||
| request_test.go | ||
| request_windows.go | ||
| server.go | ||
| server_integration_test.go | ||
| server_statvfs_darwin.go | ||
| server_statvfs_impl.go | ||
| server_statvfs_linux.go | ||
| server_statvfs_stubs.go | ||
| server_stubs.go | ||
| server_test.go | ||
| server_unix.go | ||
| sftp.go | ||
README.md
sftp
The sftp package provides support for file system operations on remote ssh
servers using the SFTP subsystem. It also implements an SFTP server for serving
files from the filesystem.
usage and examples
See godoc.org/github.com/pkg/sftp for examples and usage.
The basic operation of the package mirrors the facilities of the os package.
The Walker interface for directory traversal is heavily inspired by Keith Rarick's fs package.
roadmap
- There is way too much duplication in the Client methods. If there was an unmarshal(interface{}) method this would reduce a heap of the duplication.
contributing
We welcome pull requests, bug fixes and issue reports.
Before proposing a large change, first please discuss your change by raising an issue.
For API/code bugs, please include a small, self contained code example to reproduce the issue. For pull requests, remember test coverage.
We try to handle issues and pull requests with a 0 open philosophy. That means we will try to address the submission as soon as possible and will work toward a resolution. If progress can no longer be made (eg. unreproducible bug) or stops (eg. unresponsive submitter), we will close the bug.
Thanks.