Your best friend for file transfer.

Fetch application logoFetch

fetch's buffers (2 posts)

This is an archived topic. The information in it is likely to be out-of-date and no longer applicable to current versions of Fetch.
  • Started 23 years ago by rosmifetch
  • Latest reply 23 years ago from Jim Matthews
  • rosmifetch Member

    history- we have several older machines (4 9500s, 1 8600 and 2 7300s) running os 7.6.1 and ftping postscript files to our Sun-based RIPS using applescript to control anarchie. Our best attempts have failed at upgrading the systems to os 9 or newer versions of anarchie.
    We've bought a bunch of g4-cubes to replace the existing hardware and once again did our tests. I rewrote the applescript from scratch so that I could try anarchie, URL access, and Fetch. Arachie still eventually fails, locking up the machines.
    Fetch 3.0.3 doesn't fail. It runs pretty well. We like Fetch ;
    We do have a problem, though. Some of the files that are transferred to the rips through the new cubes generate postscript errors. But when we resend the same pages through the old hardware, the pages process ok.
    The main difference that I can see why Fetch works better than anarchie on newer hardware is the size of the transfer buffers... Fetch has 128k buffers, anarchie has 64k.
    With a fast network, is there a chance for Fetch to get a buffer underrun or send out munged packets? We have a good network- gigabit interconnects from switches to Foundry router, Foundry backbone, HP/Foundry switches, and 100mb connections from the macs to the sun boxes. I've seen the cubes push Fetch to over 10MB a sec on a large file transfer.

    this is the meat of my applescript- its in an idle handler and a couple of repeat loops to traverse folders on a mac:
    tell application "Fetch 3.0.3"
    put into url curdfurl item alias myitem
    close transfer window 1
    end tell

    Posted 23 years ago #

  • Jim Matthews Administrator

    I have not had reports of high-speed transfers getting corrupted. Have you compared the corrupted files to the originals, to get a sense of how the files are corrupted (e.g. are they truncated, or is data missing from the middle of the file, or is there new data that shouldn't be there)?

    I would also recommend trying Fetch 4.0b5, so see if that makes any difference.

    Posted 23 years ago #

Topic closed

This topic has been closed.