f74c4cc83c
This uses Netty's global traffic shaping handlers to limit the rate at which packets can be sent and received. If the bandwidth limit is hit, we'll start dropping packets, which will mean remote servers send traffic to us at a much slower pace. This isn't perfect, as there is only a global limit, and not a per-computer one. As a result, its possible for one computer to use all/most bandwidth, and thus slow down other computers. This would be something to improve on in the future. However, I've spent a lot of time reading the netty source code and docs, and the implementation for that is significantly more complex, and one I'm not comfortable working on right now. For the time being, this satisfies the issues in #33 and hopefully alleviates server owner's concerns about the http API. Remaining problems can either be solved by moderation (with help of the //computercraft track` command) or future updates. Closes #33 |
||
|---|---|---|
| .. | ||
| apis | ||
| asm | ||
| computer | ||
| filesystem | ||
| lua | ||
| terminal | ||
| tracking | ||