fierYice's Journal: Network bandwidth throttling...

It has come to my conclusion that bandwidth throttling should be done by the operating system per process on all varieties of "sockets." Numerous applications allow you to throttle how much up and down stream bandwidth they consume so I ask why not include such a mechanism in windows and linux? First kernel development with command line utitlities to control and view each processes setup but eventually you could build in common components to "accessing methods" to all program interfaces. Running your app, snag that bar on the side and slam down its disk i/o or network i/o settings while it is in the system tray. By building this into the operating system layer a common "process interface" can be developed for any data access method. Each "Fido" interface would naturally have a gui component later on by making it data interface independant. All applications can use this from a users standpoint simply because I should be the one who tells my computer how important any action is to me. Novice users could have a simplified interface with settings like "Used Frequently, Rarely Used, Never Used", etc. These common "templates" for basic users could help them eleviate the "lag" that all current multi-tasking environments managed. Multi-tasking your processes in the OS isn't enough, it should multi-task the entire input and output methods for accessing everything, not just "executing instructions." Advanced configuration is a must; please microsoft don't hide settings from me in an ADVANCED tab... :P