Hi all -
I am using Yummy FTP in a kiosk scenario. It's a fantastic ftp program, but I've been having some difficulties. Some background: these kiosks were built for the 2010 Olympics in Vancouver and they've seen alot of use - probably about 400 users/day. The app I built produces 2 files every time the kiosk is used, and those 2 files are each destined for upload. Every 30 secs an applescript does the following: 1) It checks if yummy is idle, and 2) checks if yummy can connect to the server. If both those conditions are met, the script will move the 2 files into 2 separate upload folders, and in each folder there is an FTP watcher (set to archive & upload). The FTP watchers then upload the files and archive them in a timestamped folder.
Well, this is theoretically how it is to work. In reality, at the end of each day, I find many files that are left in the "Processing" state, i.e. in a "Processing" folder inside the time-stamped folder that the FTP Watchers create. Now, some of these are caused by Yummy crashes, which makes sense. But the number of crashes we experience compared to the number of files left in the "Processing" state don't match (by quite a large margin - many more files left in Processing than crashes). So could there be another explanation for why uploads are abandoned?
Something to note could be the quality of the internet connection: It's very weak, and it stalls often.
I've set up the error settings for maximum stealth, i.e. infinite upload tries and auto-dismiss errors (thanks to forum member JD!). However, there are many more settings and I'm not sure which could be the magic bullet here..
Anyways, I hope I haven't bored you! Any help would be greatly appreciated, especially from JD or other experienced folks. Thanks!
Gabe Mastey
Tactual Systems Inc.









Logged

