I think in terms of TRAFFIC management sending a large .pdf will just cause a unnecessary Log-Jam.
If we want to send that type of content it needs to be broken up into smaller chunks.
Either say .pdf chapters and then put back together or multi part zip.
Multi-part Zip has the disadvantage that you can not look at the file until you have all the parts.
The third and most sensible is to implement multiplexing software at the transmitting end and and reverse multiplexing at the receiving end.
That way many files can be sent at the same time, based on a priority structure which will determine which goes first.
Many routers do this, i.e. voice packets first, video next, HTTP next and non time sensitive last i.e. ftp of downloading bulk files.
In the Outernet 20 MB a day case the the data Multiplexer hierarchy might be:
News Ticker = first /Real time
Major News Update = within 60 seconds
Tweets=fast / minutes
Text Emails= Soon-ish / within 5 min
Hourly news report files = within 60 minutes.
Popular Webpages requests= Within 4 hours
Email attachments = within 24 hours.
Background bulk files = Last / Whenever.