[twsocket] TIpFtp: suspicious code and other
TCustomFtpCli.DoGetAsync contains lines to open file stream. But as far as I see exactly the same is implemented in CreateLocalFileStream method. Maybe it would be better to call it instead? I would also like to know how can I attach to the moment of creating file to write. I want to set Hidden attr to files being downloaded and clear it on download finish, but I don't know where to place it. I could make OpenFileStream virtual but it's used in other places too - so it's hard to distinguish one case from another. Currently I see only one way: check OpenMode in OpenFileStream to determine whether the file is being opened for writing or not. Maybe you've got better ideas? -- Anton -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TIpFtp: suspicious code and other
Anton Sviridov wrote: I would also like to know how can I attach to the moment of creating file to write. I want to set Hidden attr to files being downloaded and clear it on download finish, but I don't know where to place it. I could make OpenFileStream virtual but it's used in other places too - so it's hard to distinguish one case from another. Currently I see only one way: check OpenMode in OpenFileStream to determine whether the file is being opened for writing or not. Maybe you've got better ideas? There's property TFtpClient.LocalStream. See button Transmit using a stream in OverbyteIcsFtpTst demo. -- Arno Garrels -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
