On 05.02.2018 20:47, Basin Ilya wrote:
> Hi.
> I noticed that commons-parent p
Hi.
I noticed that commons-parent pom has this:
${scmBranch}@r${buildNumber}; ${maven.build.timestamp}
and it is used as `Implementation-build:` jar manifest entry.
Is it a standard or a tradition? Is it for svn only? What about git?
besides, for servers that don't support async NOOPs we
don't have to
wait in __noop()
I think that what we need to do is to collect (#NOOPs + 1) responses at the end
with a read timeout 10s, filter out 500 and 200 and the remaining status will
be 226 or an
error status.
On 19.10.2017 2
Ok, so I found these two that support it:
- BulletProof FTP Server
- Pure-FTPd
Will test further.
On 17.10.2017 18:29, sebb wrote:
> On 17 October 2017 at 16:01, Basin Ilya <basini...@gmail.com> wrote:
>> Hi sebb
>>
>>> No, because some FTP servers *do* support
Hi sebb
> No, because some FTP servers *do* support asynchronous control channels.
Do you know any?
On 17.10.2017 17:54, sebb wrote:
> On 17 October 2017 at 12:34, Basin Ilya <basini...@gmail.com> wrote:
>> Hi.
>> I'm using
>> FTPClient.retrieveFileStrea
Hi.
I'm using
FTPClient.retrieveFileStream()
and therefore I need to implement keepalive mechanism by my own.
I wanted to mimic the implementation from FTPClient.CSL, but then I thought:
Most FTP servers don't reply to NOOPs until transmission has finished and yet,
sending NOOPs helps to keep
