Re: [v16.3 64 IC on El Capitan] Receive file

[Jörg Knebel via 4D_Tech]

> On 5 Sep 2018, at 10:40 AEST, Keisuke Miyako via 4D_Tech 
> <4d_tech@lists.4d.com> wrote:
> 
> of course. that is not a good enough excuse,
> but I wanted to mention it as a weak explanation.

Thanks Keisuke.

That means I’ll use your cURL only.

**
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: [v16.3 64 IC on El Capitan] Receive file

[Keisuke Miyako via 4D_Tech]

I don't mean that it is obsolete or deprecated.

I mean that the basic design and feature set is pretty much the same as v6.8 
(1999)
because the focus has been placed on keeping it alive, not to give it a new 
life.

true, there have been efforts over the years to support Unicode, UDP, TLS email 
and 64-bits,
but the main driver for such updates was to prevent it from becoming a 
liability to 4D, not to make it better.

as a consequence, the plugin is a strange compromise of outdated design and a 
series of patches that sometimes contradict each other.

it is the classic new wine old skin bottle situation.

2018/09/06 5:14、Richard Wright via 4D_Tech 
<4d_tech@lists.4d.com>のメール:
Can you clarify "in fairness, it is legacy software, free to use and not part 
of the main product line.”
There is a 64 bit version 4D Internet Commands which tells me it’s being 
updated and I see nothing to indicate that it is considered legacy.


**
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: [v16.3 64 IC on El Capitan] Receive file

[Richard Wright via 4D_Tech]

Can you clarify "in fairness, it is legacy software, free to use and not part 
of the main product line.”

There is a 64 bit version 4D Internet Commands which tells me it’s being 
updated and I see nothing to indicate that it is considered legacy. 


Richard Wright
DataDomain
rwri...@datadomainsoftware.com



> Date: Wed, 5 Sep 2018 00:40:30 +
> From: Keisuke Miyako 
> 
> 
> I think you are referring to ACI0096897 which is described as standard 
> behaviour, that is,
> expected result according to design.
> 
> FTP_GetDirList uses the 'LIST' request.
> When optionnal output parameter if provided to get timestamps, it sends an 
> 'MTDM' request for each file of the directory.
> (and not the 'MLSD' request of RFC 3659)
> 
> the result is that FTP_receive returns error 10048 on certain servers, since 
> 15.4 (was ok until 15.3)
> the workaround is to
> a: not provide last optional array for timestamps in FTP_GetDirList,
> or
> b: call  FTP_Login again after FTP_GetDirList
> 
> the fact that the bug is considered standard behaviour,
> speaks for itself about the level of enthusiasm to maintain the product.
> 
> in fairness, it is legacy software, free to use and not part of the main 
> product line.
> 
> of course. that is not a good enough excuse,
> but I wanted to mention it as a weak explanation.



**
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: [v16.3 64 IC on El Capitan] Receive file

[Jörg Knebel via 4D_Tech]

> On 5 Sep 2018, at 11:35 AEST, Keisuke Miyako via 4D_Tech 
> <4d_tech@lists.4d.com> wrote:
> 
> which has an API similar to 4DIC.

Thanks


Regards
Jörg Knebel, M.Eng. - 4D Developer since 1991
TTT Data Systems Pty Ltd
Phone: +61 (0)2 6601 7453
www.tttdatasystems.com.au 
**
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: [v16.3 64 IC on El Capitan] Receive file

[Keisuke Miyako via 4D_Tech]

for FTP,

it might be easier to use the specialised version

https://github.com/miyako/4d-plugin-curl-ftp

which has an API similar to 4DIC.

2018/09/05 10:33、Jörg Knebel via 4D_Tech 
<4d_tech@lists.4d.com>のメール:

I might be blind and/or to old, but I couldn’t figure out how to do the 
equivalent to “FTP_GetDirList” in cURL before attempt to do a dowload…



**
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: [v16.3 64 IC on El Capitan] Receive file

[Jörg Knebel via 4D_Tech]

> On 5 Sep 2018, at 10:40 AEST, Keisuke Miyako via 4D_Tech 
> <4d_tech@lists.4d.com> wrote:
> 
> of course. that is not a good enough excuse,
> but I wanted to mention it as a weak explanation.

Thanks Keisuke.

That means I’ll use your cURL only.

Wich brings me to the next questions.

Is there a detailed manual for your plugin with “how to use …”?

I might be blind and/or to old, but I couldn’t figure out how to do the 
equivalent to “FTP_GetDirList” in cURL before attempt to do a dowload… 

Cheers
Jörg


Regards
Jörg Knebel, M.Eng. - 4D Developer since 1991
TTT Data Systems Pty Ltd
Phone: +61 (0)2 6601 7453
www.tttdatasystems.com.au 
**
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: [v16.3 64 IC on El Capitan] Receive file

[Keisuke Miyako via 4D_Tech]

I think you are referring to ACI0096897 which is described as standard 
behaviour, that is,
expected result according to design.

FTP_GetDirList uses the 'LIST' request.
When optionnal output parameter if provided to get timestamps, it sends an 
'MTDM' request for each file of the directory.
(and not the 'MLSD' request of RFC 3659)

the result is that FTP_receive returns error 10048 on certain servers, since 
15.4 (was ok until 15.3)
the workaround is to
a: not provide last optional array for timestamps in FTP_GetDirList,
or
b: call  FTP_Login again after FTP_GetDirList

the fact that the bug is considered standard behaviour,
speaks for itself about the level of enthusiasm to maintain the product.

in fairness, it is legacy software, free to use and not part of the main 
product line.

of course. that is not a good enough excuse,
but I wanted to mention it as a weak explanation.

> 2018/09/04 22:07、Jörg Knebel via 4D_Tech <4d_tech@lists.4d.com>のメール:
> Any useful explanation for that one?



**
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

[v16.3 64 IC on El Capitan] Receive file

[Jörg Knebel via 4D_Tech]

Hi,

It was on the list before, but there was no solution/workaround offered.

So, I tried to do a very simple FTP-file-download the following way:

$vtxt1:=$remotePath+$filename   
$vtxt2:=$localPath+$filename
case of
: (FTP_Login ($ftpHost;$ftpUser;$ftpPassword;$FtpID;$WelcomeText)#0)

: (FTP_Receive ($FtpID;$vtxt1;$vtxt2;0)#0)
TRACE

: (FTP_Logout ($FtpID)#0)
Else 

End case 

At "FTP_Receive ($FtpID;$vtxt1;$vtxt2;0)” an error -54 “Connection reset by 
peer” is thrown at me.

I can use "FTP_Delete ($FtpID;$RemotePath)straight after and it will work, 
meaning the file will be deleted at the remote directory.


Any useful explanation for that one?


I use the cURL-PlugIn as workaround (Thanks Keisuke), but would appreciate a 
working 4D IC.


Regards
Jörg Knebel, M.Eng. - 4D Developer since 1991
TTT Data Systems Pty Ltd
Phone: +61 (0)2 6601 7453
www.tttdatasystems.com.au 
**
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**