Mine goes about 60 hours now. Check ebay for a 2450mAh battery. They sell for about eight bucks.
Or put the bar at something innovative, like 10 mbps symmetric.
> If you were to lower round trip cost of subsequent session setup
*waves magic wand*
Well that didn't work...
TLS/SCTP is the application that no one knows that they need.
Mostly agree with the parent comment.
Note that helmet-mounted bluetooth interfaces have existed for years, and many mid-to-upper range helmets are designed for those optional systems. Take away the HUD, add a modern smartphone, and I have all the Skully's useful-to-me features at a fraction of the cost.
The "new" news is the release on the A8-7600; and only about 7 months late. Most of the reviews for that processor were published in January, which is shameful really.
But now that it is out, it is at a good price, decent computationally, very good power envelope. It's a good option for productivity-only desktops, at a fraction of the price of a 7850K or an i3-4330.
They shouldn't. Two other positions exist which would be more to libertarian liking.
One option would be to oppose the sanctioned monopoly that net neutrality supporters want to regulate. By providing competition, it will be easy for the free market to punish ISPs who choose to discriminate between traffic sources. A side effect of this choice is a snarl of wires on the telephone poles - one for each local ISP. Also, this option is unlikely to work where all communications lines have been buried.
Libertarians could compromise to a second option - the common carrier option. This position yields the physical connection to stringent government control (like telephone networks, power grid, etc) but allows any company to make use of said infrastructure. Essentially, the wire is socialized, but everything that it carries is free-market.
Get off my lawn, noob.
How do you put up a parking page that listens on loopback?
By sitting in a board room without any clue where your money comes from.
Can anyone come up with a sensible reason to implement such a thing?
Or, perhaps, you were hired to find a scapegoat. Honestly, who cares; they need the project to work, so make it work.
The project is yours. Guess a rewrite timeline, send it to your boss, and get to work. While they bicker on it, send them updates. If you are going to get fired, it was going to happen anyway; you can still do good work in the meantime.
The typical VoIP packetization interval is 20ms. At their highest bitrate, you would be transmitting 48 bits (or 6 bytes) of data per packet.
However, RTP packets have 54 bytes of overhead, and 20ms of G.729 is 20 bytes. Switching from G.729 to codec 2, the net bandwidth would only be a 19% decrease in bandwidth. For comparison, the last widespread codec change (G.711 to G.729) was a 65% decrease in bandwidth. It would be a much harder sell.
On the other hand, VoIP could use the bandwidth for redundancy; perhaps a moving window of 60ms every 20 ms to protect against single packet loss. It could happen...
They do have a way. They asked if it had already been determined.
The correct response is, "We don't know."
Am I the only person that read the headline and thought CPU? Misled?
The judgement of the responding officer was to file a report. Sensible enough. The arrest happened a week later.
RTFA. This opinion is not applicable.
Also, "I win this debate" while the opponent is in mourning. Classy.