The following is my (nearly verbatim) final beta test Report for iGet, reproduced here by permission of the software development team:   

" . . . major complaint is SPEED, or lack of same. Speed of file transfers must always be the primary concern of admins and users alike. As a not-entirely scientific test I performed multiple uploads and downloads with iGet SIMULTANEOUS with an equal number of file transfers utilizing (haxial's) "KDX Client." [KDX file transfers are encrypted and function on a Server - Client and/or (Peer-to-Peer) basis. [ K D X is fully platform-independent and does NOT conform to Apple's A.P.I.s. It is completely cross-platform, including interfaces for BSD, OS X, Linux, WinXP, etc.]

iGet file transfers were generally in the range of from 1 - 3 K/sec. (on a Cable Modem connection.) KDX got 3 - 6K /sec with 4 files at a time, and with 2 files, 4 - 8K/sec each. For comparison purposes only my downloads from a selection of standard web pages ranged from 45k/sec to over 500k/sec [utilizing "Speed Download"]

A major annoyance was experienced immediately as iGet does NOT report the ongoing or the final speed of file transfer or estimated time to completion. These are available in all of the P - to - P applications that I have tried as both user and admin' over the last 12 years.

The following is a illustrative representative sample:

2004-06-30 17:30:03 -0400: Task started.
2004-06-30 17:30:03 -0400: Requesting upload...
2004-06-30 17:31:28 -0400: Will start transfer stream...
2004-06-30 17:31:28 -0400: Total transfer size will be 2.51 MB.
2004-06-30 17:52:51 -0400: Complete.
2004-06-30 17:53:35 -0400: Transfer complete.
2004-06-30 17:53:35 -0400: Task completed.
2004-06-30 17:53:35 -0400: Elapsed time: 1411.547 sec.

The computation required to determine the actual speed -- after the fact . . .

2.51 x 1,024 / 1,412 = 1.8K / sec.

On balance, iGet has a nice clean uncluttered basic no-frills user-friendly and intuitive interface. Perhaps the "newbie" would be stumped by his inability to understand the File Permissions in the "Get Info" windows, but that is splitting hairs as (s)he has no "need to know."

It is important for end-users to realize that iGet utilizes OS X's File Sharing, and, security concerns aside, this requires that the other party share with you BOTH her Mac's I.P. address AND her PASSWORD. This needs to be borne in mind.

I believe that if the speed of file transfers can be ratcheted up by a factor of 2 or 3 then iGet can be viewed as a seriously valuable tool on a LAN or on a wireless Airport Extreme network. I would not hesitate to recommend it as an affordable and uncomplicated alternative to First Class Client / Server, etc.