Re: [twsocket] 64-bit FTP support

2005-10-24 Thread Arno Garrels
Angus Robertson - Magenta Systems Ltd wrote: I've finished updating the ICS FTP client and server components to support 64-bit streams and thus single files larger than 2 gigs, when used with Delphi 6 and later. The updated components may be downloaded from:

Re: [twsocket] 64-bit FTP support

2005-10-24 Thread Angus Robertson - Magenta Systems Ltd
Angus, I took a brief look at your code (btw: I couldn't find it in the new ICS Beta from yesterday). Nor I, it's been lost. Large files can only be used in the client with TFileStream, since THandleStream and TMemoryStream don't support sizes larger than 2 gigs, THandleStream

Re: [twsocket] 64-bit FTP support

2005-10-24 Thread Francois Piette
I think it can be simplified, without an own Seek64-function just by a new custom integer type that would be of Type Int64 in D6 and above. Yes, that's what I told to Angus when I saw his code. Introducing this datatype would dramatically reduce conditional compilation. -- [EMAIL PROTECTED]

Re: [twsocket] 64-bit FTP support

2005-10-24 Thread Arno Garrels
Angus Robertson - Magenta Systems Ltd wrote: You could probably simply overload GetFileSize() and DecodeMlsResp() as well. Was overloading supported in Delphi 1? No idea, however you could also move condional compilation into the various helper functions some like the untested lines below.

Re: [twsocket] 64-bit FTP support

2005-09-07 Thread Dan
- Original Message - From: Angus Robertson - Magenta Systems Ltd [EMAIL PROTECTED] To: twsocket@elists.org Sent: Wednesday, September 07, 2005 12:53 AM Subject: Re: [twsocket] 64-bit FTP support Are you sure you were using soBeginning, soEnd etc. instead of soFromBeginning, soFromEnd

Re: [twsocket] 64-bit FTP support

2005-09-06 Thread Arno Garrels
Angus Robertson - Magenta Systems Ltd wrote: I've finished updating the ICS FTP client and server components to support 64-bit streams and thus single files larger than 2 gigs, when used with Delphi 6 and later. Great, things move! Testing was probably a lengthy story with such large files

Re: [twsocket] 64-bit FTP support

2005-09-06 Thread Angus Robertson - Magenta Systems Ltd
Testing was probably a lengthy story with such large files ;-) Around five to six minutes for 4.6 gig download across my LAN, it's supposed to be gigabyte speed but it's only Netgear components and I don't really see the speed I'd expect. Uploads are at least half the speed. Also quite a

Re: [twsocket] 64-bit FTP support

2005-09-06 Thread Arno Garrels
Angus Robertson - Magenta Systems Ltd wrote: Testing was probably a lengthy story with such large files ;-) Around five to six minutes for 4.6 gig download across my LAN, it's supposed to be gigabyte speed but it's only Netgear components and I don't really see the speed I'd expect. Uploads

Re: [twsocket] 64-bit FTP support

2005-09-06 Thread Angus Robertson - Magenta Systems Ltd
I would bet that a buffered stream class would boost performance dramatically. I do recall a recent discussion about buffered class, but can not find it. Note sure how easy it would be to add, due to some of the 64-bit issues. The FTP server is crying out for a file buffer system, so that

Re: [twsocket] 64-bit FTP support

2005-09-06 Thread Arno Garrels
Angus Robertson - Magenta Systems Ltd wrote: I would bet that a buffered stream class would boost performance dramatically. I do recall a recent discussion about buffered class, but can not find it. Note sure how easy it would be to add, due to some of the 64-bit issues. I never got

Re: [twsocket] 64-bit FTP support

2005-09-06 Thread Dan
- Original Message - From: Angus Robertson - Magenta Systems Ltd [EMAIL PROTECTED] To: twsocket@elists.org Sent: Tuesday, September 06, 2005 4:45 PM Subject: [twsocket] 64-bit FTP support ... proved a pain during testing because the integer overloaded Seek seemed to be linked rather

Re: [twsocket] 64-bit FTP support

2005-09-06 Thread Angus Robertson - Magenta Systems Ltd
Are you sure you were using soBeginning, soEnd etc. instead of soFromBeginning, soFromEnd. I had this problem when I started using int64 streams and that was the solution. These have the same numeric values so should not make any difference to how the stream is used. soFromBeginning =