Re: Using the winsock gateway for FTP


[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]

Posted by Bruno Biancucci on October 06, 2006 at 07:03:02:

In Reply to: Using the winsock gateway for FTP posted by Jim Guerber on January 30, 2006 at 12:46:16:

Nice sample program Jim. I was able to use it as a starting point for a recent project. I currently have a solution in place using DOS batch files, but Comet would give me more control over the whole job.

Two issues that are giving me problems. Not sure how to deal with them at this point.

My problem: I need to download multiple files and I don't know what the filenames are. The filenames include a DATE portion. They are also long names containing yyyymmdd. We're talking about 12 files with 10 megabytes of data in total.

The program works by logging into ftp site, doing an LS (or DIR) to get a list of names that saves to a temp file. I just log back in and get the files from my list. I close and reopen the ftp file between each file. There are both Text and zip files in the folder (ie. .TXT and .ZIP)

Problem #1, I have a long filename issue. The names seem to overlap when being created on local machine and I've checked the comet program to make sure I was clearning things. I basically print out my variables to the spooler (like you did to LPH), so I can see internals. I'm providing the correct filename. I do use DOS calls to create, open, write, close the files being download. It's like there is a Comet memory work area for the filename being used in the background that is being reused, but not cleared.

Problem#2, Download is much slower to download with the comet program. It's like comet is waiting for something or the FTP server is waiting for Comet to respond before ftp server sends more data. I can download same files in FTP client (Bulletproof) in about 2 minutes. Comet takes about 15-20 minutes and sometimes I'll get a communications type error. The stall is in the middle of getting data when there is more information and not at the end of the data stream when Comet does it's timeout to assume there is no more data.

So far, I have checked the files and all the informaiton seems to be there - I've only looked at about five zip files. Once I rename them to the correct extention (ie. .zipp or .zipt to .zip ) they open up and I can see and open up the images.

If I could resolve the longfilename problem, I think I would be ok with the speed problem. I would just open up multiple threads and just hit the server with more than one job at a time. I could then check list the filename list and keep doing it untill I get my files.

Oh yea, we did update the Comet Workstation to a recent one (comet2005 build .371/05.03) for the FTP to work. They had a pre-version installed - per your notes, we did this to get the Comet FTP working. One thing we didn't do was update the CometServerProducts (it's 507) iteself. We're running on a Windows 2kserver with lots of everything (cpu/disk/memory).

Any thoughts on the filename issue?



Follow Ups:



Post a Followup

Name:
E-Mail:

Subject:

What is the name of the main Signature System's Product?

Comments:

Optional Link URL:
Link Title:
Optional Image URL:

You may attach up to 5 files to your followup (see below):






[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]