If we're trying to push out 137 GiB of data there are a few numbers to consider.
137 GiB == 147 102 629 888 bytes Rounding up to 1 million byte units 147103.
802.11g (typical wireless) transfers at up to 54mbps* (no odd configurations special channels/etc), let's presume 50mbps is data and not network overhead. ( http://en.wikipedia.org/wiki/IEEE_802.11#Channels_and_international_compatibility
<< check out the graphic about network channels.)
100base* '100megabit ethernet' Aprox 90% is usable when removing various normal network overheads. 90mbps.
1000base* '1000megabit ethernet' Aprox 90% is usable when removing various normal network overheads. 900mbps.
147103 / 50 / 3600 = .817238 hours
147103 / 90 / 3600 = .454021 hours
147103 / 900 / 3600 = .045402 hours
However, there is another number; the speed I was able to get at the meeting. I was averaging approximately 1MiB/sec (during transfers), which is 8mbps.
147103 / 8 / 3600 = 5.107743 hours
Limiting factors: Typical laptop hard disk = ~5-10MiB/sec == 65 hours to write the data @ 40mbps =~ 1 hour.
Therefore the limiting speed for most users will be that of their storage media. In such an environment resumable, selective, and collaborative transfers seem to make the most sense. The only widely used and multi-platform solution that comes to my mind is bit-torrent.
It would not be difficult for me to provide a laptop with a bit-torrent tracker; in fact I was already trying to re-purpose an old laptop of mine for just such a role.
As an added bonus I'm reasonably sure that most of our users would already know how to select portions of torrents to save.