You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ftpserver-dev@incubator.apache.org by "Niklas Gustavsson (JIRA)" <ji...@apache.org> on 2007/07/14 21:19:04 UTC
[jira] Commented: (FTPSERVER-101) response.write() does not flush
the stream
[ https://issues.apache.org/jira/browse/FTPSERVER-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512740 ]
Niklas Gustavsson commented on FTPSERVER-101:
---------------------------------------------
I can not reproduce this problem, could you please provide a test case? A few things to note is, your client might not show multiple return values for one FTP request. For example, using the commons-net FTP client requires calling the completePendingCommand() to show the additional returns. Also, since the first command you return is a 1XX code, that would mean that your client must know to wait for a success response for the same command. And, your return codes are four digits, not sure if that is allowed.
> response.write() does not flush the stream
> ------------------------------------------
>
> Key: FTPSERVER-101
> URL: https://issues.apache.org/jira/browse/FTPSERVER-101
> Project: FtpServer
> Issue Type: Bug
> Components: Ftplets
> Affects Versions: 1.0-M1
> Environment: All platforms
> Reporter: ajith
> Assignee: Niklas Gustavsson
> Priority: Critical
>
> Calls to response.write() does not flush the stream. As a result only some of the responses is written when more than one call to response.write() is made. For eg:
>
> response.write(1234, "test");
> //do something
> response.write(2345, "test");
> return FtpletEnum.RET_SKIP;
> does NOT print
> 1234 test
> 2345 test
> on the client terminal.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.