On high overload factors (common on consumer ISPs), simply limiting per application/protocol, does not decongest the network enough. Example: VoIP - if everybody and their grandma are using it, who cares you've practically shutdown torrent trafic, the routers are still overloaded, and latency is crap, the application itself, or the OS should throttle on request via ECN, or dropping packets at the inbound edge routers ought to usually provide then needed behavior - though you need ECN in the network always. That's not very common, AFAIK.
HTTP and Bittorrent are not transport (OSI link/session) protocols, they are presentation/application protocols, depending on usage. As for TCP, it has congestion a avoidance algorithm - ECN, and IMHO would work well with buffers, but AFAIK, no one uses it.
Slashdot Mirror
Do the rails make such a difference in friction? And have you heard of electromobiles? There is much more car per passanger, than per train (safety) ?
Agreed, though as teenager, I must complain of the lack female sex offenders.
Can localized application of anabolic steroids be of any help?
What if you take pictures, and note down the chip numbers, and make yourself a TV from materials you bought?
I'm waiting for version 3.11 for workgroups.
Speaking of k3b, did anyone fix the burning CD bug in Fedora 13?
I believe a well maintained external repository is just as good. To each his own.
Facebook is an OpenID provider.
Give me time.
Ah, now that was what I was looking for. Thanks for the clarification. Though AFAIK windows has similar issues, but whatever.
Flash supports WebM as well. And there are HTML5 JS libs that can fallback to Flash from the video tag.
Define official.
It's also easily found on amd64 systems.
See here.
Except for AMDs hidden debug mode...
That's it - I'm going into hardware hacking - just to be able to do that - piss of the anti-pirate and the think of the children crowd at ONCE!
Your point is? The rpmforge website is apparently cited on the fedora project website, as it is listed here. What else do you want?
LED growlights and a battery pack, my friend.
How about sane defaults on the web sever? Have it set by file.
ECN ought to take care of that.
On high overload factors (common on consumer ISPs), simply limiting per application/protocol, does not decongest the network enough. Example: VoIP - if everybody and their grandma are using it, who cares you've practically shutdown torrent trafic, the routers are still overloaded, and latency is crap, the application itself, or the OS should throttle on request via ECN, or dropping packets at the inbound edge routers ought to usually provide then needed behavior - though you need ECN in the network always. That's not very common, AFAIK.
HTTP and Bittorrent are not transport (OSI link/session) protocols, they are presentation/application protocols, depending on usage. As for TCP, it has congestion a avoidance algorithm - ECN, and IMHO would work well with buffers, but AFAIK, no one uses it.
Buffering, with ECN and slight bandwidth overestimation ought to solve that, thing is, no one uses ECN, AFAIK.
SCTP
53 bytes, actually, and ATM sucks for a whole lot of reasons, which I'm not going to detail here - Google is your friend.