We can only send packets as fast as they come out of the codec. After you've just transmitted a packet, there's maybe a 100mS wait until the next packet even exists. As long as Skype (or any VOIP stack) is working properly, the senders do all the 'flow control' necessary, simply by having a constant, regular stream to transmit.
You don't want TCP flow control at all, you've either got enough bandwidth or you haven't.
You generally use UDP for voice because if a packet gets delayed or lost, there's no point in retransmitting it. In fact, retransmission would cause delays, whereas a missing packet is usually handled quite well by whatever endpoints are in use (i.e. they just repeat the audio in the last packet received, and hope the user doesn't notice).
Well, if you're going to be that pedantic, the data still goes through an encoding layer called "Eight to fourteen modulation", which guarantees that a pit / land will be at least x bits and no more than y bits long, so the laser won't lose tracking due to not finding any transisions in a long time.
So, according to TFA, this card is supposed to reduce lag/latency. The big question for me is this: will it make any difference if the server you're trying to play on is having trouble? I know that 90% of the lag I get is caused by low bandwidth on the server side, not the NIC on my end.
Amazingly, yes.
The 'Killer' sends packets so strong that any congestion encountered along the way gives up its place in the queue. Utilising the unique HellGain (TM) technology, pulses are transmitted with more energy than other NICs
Also, for those using half-duplex on hub ports, there's the CollisionKiller (TM) feature. When collisions are detected, your card keeps transmitting, but one-louder. Depending on the congestion on the segment, up to 500V could be present at the connector.
Given how thin on the ground IPv6 is at present, it's more than an opportunity for them to get in and do something stupid like implement ActiveX at Layer 2, if that's possible. I'm sure they dream of closed lower-layer networking protocols and given the chance could explain ten ways things like Ethernet have held back development and supported terrorism.
All true.
I thought I'd never end up going digital, but I can't find any good 35mm labs here any more. It's pretty depressing spending minutes sometimes setting up exposures, apertures, etc., only to see JPEG artifacts on the prints.
Took them back to the lab, yelled "WTF", and while he agreed there were noticable artifacts on the images, they were 'good enough for most people' because nobody before me had noticed.
For me, while digital has lowered the price plenty, it's also lowered the bar.
Great idea. In the process, you completely nullify what the system purpotedly did in the first place, since you can't verify your real vote any better than (any of the) fake one(s).
You don't even need to be using TCP/IP. Broadcasting and multicasting are supported by at Layer 2 by Ethernet and most LAN technologies. What you do in the routers to get the packets across WAN links is up to you, but it doesn't have to be TCP/IP.
So many sysadmins I see make their own job a misery by alienating users and doing an all round shitty job. I knew one who, rather than running using a routing protocol or getting it right in the first place, distributed scripts to change a users default gateway depending on what service they wanted to use. Countless times they forgot to change it back, and he'd belittle them. One day he left, and I replaced him.
My first memo: "Throw those scripts away guys. You can now leave your default gateway alone and everything should 'just work'". At first they were amazed at what I'd done, some of them asked me what it was. I said "Your sysadmin does his job now, so you only need to worry about doing yours."
Fellow admins: Don't hate your users. They're the only reason you're needed, and they're all well aware of your expertise, so don't push it on them. I love it when my users tell me how much more approachable I am than the last guy, and this happens more often than once a year, so I don't need no stinkin Sysadmin Appreciation Day.
Nice work on the article timing, Hemos. I know the OCT 31 ~= DEC 25 joke and all that, but don't get this "Two weeks to go" business.
And it's kind of already October 31 for some of the globe. I don't know what kind of timezone the slashdot editors are in, but that's a far cry from two weeks away.
Slashdot Mirror
In Linux Netfilter it's hardcoded at 30S apparently. It's purely implementation dependant, and a function of the NAT device, not the IP spec.
We can only send packets as fast as they come out of the codec. After you've just transmitted a packet, there's maybe a 100mS wait until the next packet even exists. As long as Skype (or any VOIP stack) is working properly, the senders do all the 'flow control' necessary, simply by having a constant, regular stream to transmit. You don't want TCP flow control at all, you've either got enough bandwidth or you haven't.
You generally use UDP for voice because if a packet gets delayed or lost, there's no point in retransmitting it. In fact, retransmission would cause delays, whereas a missing packet is usually handled quite well by whatever endpoints are in use (i.e. they just repeat the audio in the last packet received, and hope the user doesn't notice).
There are no .4 length characters!
Oh, you're so going to love it when you discover Unicode.Well, if you're going to be that pedantic, the data still goes through an encoding layer called "Eight to fourteen modulation", which guarantees that a pit / land will be at least x bits and no more than y bits long, so the laser won't lose tracking due to not finding any transisions in a long time.
Amazingly, yes.
The 'Killer' sends packets so strong that any congestion encountered along the way gives up its place in the queue. Utilising the unique HellGain (TM) technology, pulses are transmitted with more energy than other NICs
Also, for those using half-duplex on hub ports, there's the CollisionKiller (TM) feature. When collisions are detected, your card keeps transmitting, but one-louder. Depending on the congestion on the segment, up to 500V could be present at the connector.
The "proper" solution would be to find the jackass repsonsible for all this shit and beat him with in a inch of his fucking life.
That's 25.4 millimetres for those of us who use real standards.Sheesh!
...and they do nothing.
Whoa. Curveball.
It seems as if even though people want a consistent definition of 'planet', they still want the status of being one to have some prestige.
Can I get a purchase order number, please?
They *edit* Survivor?
If you're lucky enough to find some sort of intelligent debatye on a phpBB, you'll know why.
You should disable pipelining if you're getting that many emails from only 5.5 connections per week!
Given how thin on the ground IPv6 is at present, it's more than an opportunity for them to get in and do something stupid like implement ActiveX at Layer 2, if that's possible. I'm sure they dream of closed lower-layer networking protocols and given the chance could explain ten ways things like Ethernet have held back development and supported terrorism.
I thought I'd never end up going digital, but I can't find any good 35mm labs here any more. It's pretty depressing spending minutes sometimes setting up exposures, apertures, etc., only to see JPEG artifacts on the prints.
Took them back to the lab, yelled "WTF", and while he agreed there were noticable artifacts on the images, they were 'good enough for most people' because nobody before me had noticed.
For me, while digital has lowered the price plenty, it's also lowered the bar.
Great idea. In the process, you completely nullify what the system purpotedly did in the first place, since you can't verify your real vote any better than (any of the) fake one(s).
You don't even need to be using TCP/IP. Broadcasting and multicasting are supported by at Layer 2 by Ethernet and most LAN technologies. What you do in the routers to get the packets across WAN links is up to you, but it doesn't have to be TCP/IP.
protip: Say both "youtube" and "utube" out loud. Report your findings.
Hehe, I just popped over to "eyepod.com", sure as hell some hopeful squatter has it.
They'll probably start a whole new lawsuit with all these hits coming in with 'slashdot.org' as the referrer...
So many sysadmins I see make their own job a misery by alienating users and doing an all round shitty job. I knew one who, rather than running using a routing protocol or getting it right in the first place, distributed scripts to change a users default gateway depending on what service they wanted to use. Countless times they forgot to change it back, and he'd belittle them. One day he left, and I replaced him.
My first memo: "Throw those scripts away guys. You can now leave your default gateway alone and everything should 'just work'". At first they were amazed at what I'd done, some of them asked me what it was. I said "Your sysadmin does his job now, so you only need to worry about doing yours."
Fellow admins: Don't hate your users. They're the only reason you're needed, and they're all well aware of your expertise, so don't push it on them. I love it when my users tell me how much more approachable I am than the last guy, and this happens more often than once a year, so I don't need no stinkin Sysadmin Appreciation Day.
Nice work on the article timing, Hemos. I know the OCT 31 ~= DEC 25 joke and all that, but don't get this "Two weeks to go" business.
Oh har har bloody har!