Demeter:n4:Demeter:n4: I'm not saying it is happening in this specific case, but you would be naive to think it couldn't be done or isn't happening elsewhere. Slowing down non-time critical sessions (eg file downloads) to allow better service for time critical sessions (eg voice, video) is a sensible way to manage network congestion - even if only temporarily.
Are you referring to the traffic management policy which Spark are totally upfront about?
ETA - sorry, reading the above line, it sounds sarcastic and wasn't meant to be.
I'm referring to the fact that anyone who thinks traffic management (on whatever basis) is too resource intensive to be implemented needs to wake up and smell the coffee.
Oh, I see what you mean. I don't think that was exacly what chevrolux was implying though. I think it's more the assumption that ISP's are capable of scrubbing data at file level to pick/choose which exact packets to drop. If you want to split hairs, yep, technically it is totally possible but the resources needed for this type of granular control are just mindbogglingly massive.
No doubt a 2TB portable harddrive was 'mindbogglingly massive' in times past. But things change. Scrubbing data at byte level is completely practical - but still takes time and resources such that you would only do it for good reason. However scrubbing data based on (eg) which site you are on, or which file name you download, is trivial and within the capability of any traffic management system.