[ 
https://issues.apache.org/jira/browse/SSHD-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16447459#comment-16447459
 ] 

Zhenliang Su commented on SSHD-814:
-----------------------------------

Thanks.
1. Yes, there are no such SFTP command 'upload/download'. There are some 
situation that do something after downloading or uploading. For now, my way to 
approach this is doing something in `close` callback function and judge whether 
the file which closing is called `read/written` callback function. Is there 
some else way to do this?

2. When do a delete or rename or other action to a non-exist file or directory. 
For now, it just open failed, and not call any callback function in 
`SftpEventListener`.
My testing code is the middleman code in 
https://issues.apache.org/jira/browse/SSHD-812 .
My steps are:
1. Use filezilla sftp to the middleman, and see a list of file of the target 
server.
2. Ssh to the target server, delete a file.
3. Not refresh a filezilla, now you can still see the file which deleted just 
now.
4. Download that file.

> enrich the SftpEventListener
> ----------------------------
>
>                 Key: SSHD-814
>                 URL: https://issues.apache.org/jira/browse/SSHD-814
>             Project: MINA SSHD
>          Issue Type: Improvement
>    Affects Versions: 1.7.0
>            Reporter: Zhenliang Su
>            Assignee: Goldstein Lyor
>            Priority: Minor
>              Labels: EventListener, sftp
>
> In practice, I found that, the callback function provided by 
> SftpEventListener is not enough.  For example, the following situation is not 
> easy to be notified in a elegant way:
> {code:java}
> download files that you do not have access to
> download a file that no longer exists
> upload files to a directory without permissions
> create a new file in a directory that you do not have access to
> download or upload a file complete
> upload a zero size file
> ...{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to