So I'm living 10 years in the future I guess. I have a home server with a registered domain - I get email directly, serve my personal web content such as photo albums, program in alarms that wake me up in the morning via a distributed music system, backup the laptops I use throughout my house, cache DNS and automatically scarf data I need for managing my finances - stock quotes etc off the web.
A couple of things are a bit kludgey because I don't have a truly static IP; but that is not too far in the future. Really the only downside with that is I have to send my email out through my ISP's SMTP rather than directly.
The advantages over Google etc. are essentially unlimited space (I have 2 TB online right now) and very very fast access to the content, and I have control over the features of my setup. The disadvantage is setting up a reliable backup strategy takes some time and effort.
A year ago I used a hosting service for many of these features, but snce Cablevision made it's Boost service available with unblocked ports and dynamic DNS I moved everything to my home server.
I used this concurrency backport. It is really helpful if you are looking at a slow migration to Java 5 but want some improvements in your Java 1.4 application.
The Deca form of PBDE is allowed under RoHS as an extensive scientific review reached the conclusion that it is a benign material. Analysis of Deca-BDE found in whale blubber by radioactive carbon assay shows that it is a naturally occuring substance.
The Washington state ban is ill-considered eco-luddism without any basis in science.
I lost my mother to metastatic breast cancer 2 months ago. Part of that process was surgery followed by radiation to try to control brain mets. Unfortunately her aphasia was only temporarily relieved by this treatment. The disease ravaged her terribly - she lost motor control in one arm, the other had 2nd degree lymphedema from treatment of a cancer in her shoulder making it essentially useless. She lost the ability to walk, a tumor on one femur caused a broken hip that was inoperable. Eventually it was attack on her lungs that was fatal. It was 12 years between the time of original diagnoses of breast cancer until her death. It took 8 years for the first signs of metasticy to express.
People rarely die of metastatic brain tumors; it is the systemic attack that is fatal, eventually a critical organ becomes involved. I saw recently that John Edward's wife Katharyn now has this disease. It is a hard road they face.
The most far reaching changes to Java in Java 5 are the changes to improve support for concurrency. Generics are just syntactic sugar that improve compile time type checking. The concurrency support features offer fundamental improvements in the way you can structure your applications to take advantage of increasingly parallel hardware architectures.
From who's point of view? Certainly not a consumer who gets it home and finds that it doesn't play. It is absolutely defective as far as he is concerned, and under basic requirements of servicability for the intended use under consumer protection laws it fails miserably.
The seller of such merchandise had better be ready to deal with issues of this sort, it is part of being in business.
The backbone in between don't do much packet shaping as far as I am aware.
Backbones these days use a combination of MPLS and DiffServe to prioritize traffic by tagging based on protocol sniffing that occurs at the Label Switch Routers on the network edges. Backbones are not content neutral and for them to be so would result is significant additional capital expenditures and either increased service costs, lower connection speeds or reduced QoS for interactive services for all of us.
Content neutrality is not a technically valid or economically efficient approach to network operations. With more and more interactive services like video conferencing or high bandwidth performance intensive applications like IPTV the direction is clearly away from content neutrality.
Once you get off your ISP, other carriers have no information as to what your 'quota' for priortized traffic is, and will have no way to determine whether or not to priortize it. And they certainly won't want to burden their routers with trying to figure this out. The idea is totally unworkable.
Encrypted VoIP packets are still recognizable as VoIP packets (SRTP vs RTP). What is happening with P2P is that it is deliberately being tunneled through another protocol to try to conceal it's nature.
Content neutrality is fundamentally inefficient. You won't see it.
There are a lot of definitions of 'neutral' out there. In my opinion neutral today means not favoring traffic from a particular address or to a particular destination over other traffic. In general I am in favor of this sort of neutrality.
Content neutrality is a different sort of beast. There are sound technical reasons for not having content neutrality because the technical requirements of different sorts of traffic are different. If I am a consumer I WANT my VoP traffic to have priority over my file transfer traffic. I surely do not want a P2P session to disrupt my phone service or a streaming video I am watching in any way!
As far as your suggested 'latency tiers', I don't think this is economically efficient. It will cost more to provision your service so that ALL your traffic is treated like VOIP rather than provision your service so that just VOIP gets the low latency treatment. That will surely show up in the cost of the service, or what the ultimate capacity of the service is at a particular price point.
Pff. The first thing that everyone will do is turn on their 'interactive' flag for all traffic and we will be back where we are today.
Traffic shaping makes sense. VOIP traffic and other interactive applications SHOULD have priority over background-type operations. This is the way all well designed systems should work - your OS should give priority to screen redraws over virus scans.
As far as P2P traffic, there are ways to suss that out even if you are running it over encrypted sessions by using a variety of heuristic approaches. Rogers is just being lazy or stupid or both and deserves to be excoriated for this one size fits all approach.
I knew someone who was an employee of AT&T who was involved in the first VOIP call using a Sonus media gateway. Since Sonus was founded in 1997 I doubt that this occured prior to 1995.
OOL has two service tiers now, standard and Boost. The standard service has some sort of capping algorithm in place, plus terms of service that prohibit servers. The Boost service allows some types of servers, and currently there is no capping of Boost customers, plus 5 Mb/sec / 30 Mb/sec data rates (in actual use more like 4 and 25).
Turn the monitor off when you aren't using it. An LCD monitor is more energy efficient than a CRT. Buy a low-end video card. The high end cards are energy hogs. Use a CPU that you can scale back operating frequency on using CPUSPEED etc when the machine is idle. Don't buy more CPU speed than you need. Consider buying a low power version of the CPU you are getting.
Consider a motherboard that you can use a portable CPU on. Buy the smallest feature size CPUs. They are usually more energy efficient. Use smartd etc. to spin down your hard drives. Right now that usually means IDE drives - spinning down
SATA drives on Linux can be a challenge - it depends on kernel & drivers. Each hard drive = 10 watss Don't install more RAM than you need. Get a motherboard that allows you to turn off unneeded stuff like serial ports etc. Buy an efficient power supply. Use something like the Killawatt power meter to measure your results. Switch to compact flourescent bulbs!!
Do all this and you should be able to get into the 60-70W idle range. Since 1W-year =$1 that is $60/year. The flourescents will save you at least another $100/year.
Slashdot Mirror
What he did was also illegal in Australia.
It seems silly in retrospect, but in this kind of business (and in many others) false positives are a lot less damaging than false negatives.
So I'm living 10 years in the future I guess. I have a home server with a registered domain - I get email directly, serve my personal web content such as photo albums, program in alarms that wake me up in the morning via a distributed music system, backup the laptops I use throughout my house, cache DNS and automatically scarf data I need for managing my finances - stock quotes etc off the web.
A couple of things are a bit kludgey because I don't have a truly static IP; but that is not too far in the future. Really the only downside with that is I have to send my email out through my ISP's SMTP rather than directly.
The advantages over Google etc. are essentially unlimited space (I have 2 TB online right now) and very very fast access to the content, and I have control over the features of my setup. The disadvantage is setting up a reliable backup strategy takes some time and effort.
A year ago I used a hosting service for many of these features, but snce Cablevision made it's Boost service available with unblocked ports and dynamic DNS I moved everything to my home server.
I used this concurrency backport. It is really helpful if you are looking at a slow migration to Java 5 but want some improvements in your Java 1.4 application.
The Deca form of PBDE is allowed under RoHS as an extensive scientific review reached the conclusion that it is a benign material. Analysis of Deca-BDE found in whale blubber by radioactive carbon assay shows that it is a naturally occuring substance.
The Washington state ban is ill-considered eco-luddism without any basis in science.
I lost my mother to metastatic breast cancer 2 months ago. Part of that process was surgery followed by radiation to try to control brain mets. Unfortunately her aphasia was only temporarily relieved by this treatment. The disease ravaged her terribly - she lost motor control in one arm, the other had 2nd degree lymphedema from treatment of a cancer in her shoulder making it essentially useless. She lost the ability to walk, a tumor on one femur caused a broken hip that was inoperable. Eventually it was attack on her lungs that was fatal. It was 12 years between the time of original diagnoses of breast cancer until her death. It took 8 years for the first signs of metasticy to express.
People rarely die of metastatic brain tumors; it is the systemic attack that is fatal, eventually a critical organ becomes involved. I saw recently that John Edward's wife Katharyn now has this disease. It is a hard road they face.
But gliomas are comparatively rare compared to metastatic brain tumors. How about something to treat metastatic cancer, guys?
The most far reaching changes to Java in Java 5 are the changes to improve support for concurrency. Generics are just syntactic sugar that improve compile time type checking. The concurrency support features offer fundamental improvements in the way you can structure your applications to take advantage of increasingly parallel hardware architectures.
There's not a damn thing wrong with the disc.
From who's point of view? Certainly not a consumer who gets it home and finds that it doesn't play. It is absolutely defective as far as he is concerned, and under basic requirements of servicability for the intended use under consumer protection laws it fails miserably.
The seller of such merchandise had better be ready to deal with issues of this sort, it is part of being in business.
Why make a big stink?
Because it is a matter of public safety, that's why. Police should be following traffic laws unless they have a damn good reason not to.
Better read this:
http://www.amazon.com/QoS-MPLS-Networks-Networkin
I am curious as to what service you know of that guarantees unlimited bandwidth.
The backbone in between don't do much packet shaping as far as I am aware.
Backbones these days use a combination of MPLS and DiffServe to prioritize traffic by tagging based on protocol sniffing that occurs at the Label Switch Routers on the network edges. Backbones are not content neutral and for them to be so would result is significant additional capital expenditures and either increased service costs, lower connection speeds or reduced QoS for interactive services for all of us.
Content neutrality is not a technically valid or economically efficient approach to network operations. With more and more interactive services like video conferencing or high bandwidth performance intensive applications like IPTV the direction is clearly away from content neutrality.
Once you get off your ISP, other carriers have no information as to what your 'quota' for priortized traffic is, and will have no way to determine whether or not to priortize it. And they certainly won't want to burden their routers with trying to figure this out. The idea is totally unworkable.
Encrypted VoIP packets are still recognizable as VoIP packets (SRTP vs RTP). What is happening with P2P is that it is deliberately being tunneled through another protocol to try to conceal it's nature.
Content neutrality is fundamentally inefficient. You won't see it.
There are a lot of definitions of 'neutral' out there. In my opinion neutral today means not favoring traffic from a particular address or to a particular destination over other traffic. In general I am in favor of this sort of neutrality.
Content neutrality is a different sort of beast. There are sound technical reasons for not having content neutrality because the technical requirements of different sorts of traffic are different. If I am a consumer I WANT my VoP traffic to have priority over my file transfer traffic. I surely do not want a P2P session to disrupt my phone service or a streaming video I am watching in any way!
As far as your suggested 'latency tiers', I don't think this is economically efficient. It will cost more to provision your service so that ALL your traffic is treated like VOIP rather than provision your service so that just VOIP gets the low latency treatment. That will surely show up in the cost of the service, or what the ultimate capacity of the service is at a particular price point.
Pff. The first thing that everyone will do is turn on their 'interactive' flag for all traffic and we will be back where we are today.
Traffic shaping makes sense. VOIP traffic and other interactive applications SHOULD have priority over background-type operations. This is the way all well designed systems should work - your OS should give priority to screen redraws over virus scans.
As far as P2P traffic, there are ways to suss that out even if you are running it over encrypted sessions by using a variety of heuristic approaches. Rogers is just being lazy or stupid or both and deserves to be excoriated for this one size fits all approach.
If anything, ssh and https should be the highest priority.
No, streaming UDP based protocols have to be the highest priority, otherwise VoIP and similar applications won't work.
Ultimately the only logical way to handle this sort of thing is going to be through service tiers or other non-Net neutral mechanisms.
Out of band signaling methods like SS7 is not the same thing as PSTN-VOIP-PSTN.
I knew someone who was an employee of AT&T who was involved in the first VOIP call using a Sonus media gateway. Since Sonus was founded in 1997 I doubt that this occured prior to 1995.
My prediction is that the Yankees will spend more money than any other team. And still not win a World Series.
OOL has two service tiers now, standard and Boost. The standard service has some sort of capping algorithm in place, plus terms of service that prohibit servers. The Boost service allows some types of servers, and currently there is no capping of Boost customers, plus 5 Mb/sec / 30 Mb/sec data rates (in actual use more like 4 and 25).
It's worth the extra $10 to get Boost.
There is another article in Wired by Tufte on the topic which mentions some problems of using Powerpoint in education.
l
http://www.wired.com/wired/archive/11.09/ppt2.htm
That's called eminent domain.
It seems to me that Fritz Lang's Metropolis would be easy to cite as prior art.
Turn the monitor off when you aren't using it. An LCD monitor is more energy efficient than a CRT.
Buy a low-end video card. The high end cards are energy hogs.
Use a CPU that you can scale back operating frequency on using CPUSPEED etc when the machine is idle.
Don't buy more CPU speed than you need. Consider buying a low power version of the CPU you are getting.
Consider a motherboard that you can use a portable CPU on.
Buy the smallest feature size CPUs. They are usually more energy efficient.
Use smartd etc. to spin down your hard drives. Right now that usually means IDE drives - spinning down
SATA drives on Linux can be a challenge - it depends on kernel & drivers. Each hard drive = 10 watss
Don't install more RAM than you need.
Get a motherboard that allows you to turn off unneeded stuff like serial ports etc.
Buy an efficient power supply.
Use something like the Killawatt power meter to measure your results.
Switch to compact flourescent bulbs!!
Do all this and you should be able to get into the 60-70W idle range. Since 1W-year
=$1 that is $60/year.
The flourescents will save you at least another $100/year.