There is a backup solution by a company in Seattle called InterVault. It allows you to backup your data to their servers via the Internet. They use encryption to protect your data, so don't lose your password. Their is no backdoor. Check them out at www.intervault.net.
If they want to give her grief about the napsack, just mention the American's With Disabilites Act. That is still law in the United States, and you can sue them over it.
They had these when I was in high school. You hooked it up to a computer or VCR and placed it on the overhead projector. The problem we always had was that the intensity of the overhead projector always washed out the image. Made it tough to see what the teacher was trying to show us.
Back in the good old days, the Internet was rendundant and would route around down nodes. Back in the good old days, the Internet was also run by the National Science Foundation and the Universities. The NSF and the Universities were fairly good at keeping multiple routes up between them.
Then along came the commercialization of the Internet. As the Internet became more and more the domain of corporations rather than academics, the philosophy of Intrnet routing changed. No longer did everyone keep links to several different services. Now corporations would sign contracts with each other and charge each other to connect. This resulted in a reduction in the number of links between hosts.
Few companies can afford to link to a large number of other routing points, and those that can charge for the privledge of using them. This cycle has continued until the majority of the traffic routes through these network providers.
This leads to a situation where, if one of these goes down, all the traffic they had been routing must now be shunted down their 2 or 3 backup links. These links usually have smaller pipes and, therefore, cannot service the enormous amount of traffic being dumped on them. This results in lost packets and unreacheable destinations.
How do we fix this problem? That's the big question. The consolidation of network providers has killed the redundancy of the Internet.
At work, the biggest feature of C++ that we insist that everyone use are exceptions. Using exceptions helps us keep code clean and readable and gets rid of multiple nested if statements everytime we have to test for an error condition. The ability to throw an exception and simply catch them all at the bottom makes debugging a lot simpler.
Other features that we use include STL, for the simplicity of creating lists and other data structures, and polymorphism. Since our entire project is an object oriented design, we can't get away from it, and in many cases, it greatly reduces the amount of code we have to write and debug.
That said, however, It is important that you design your object heirarchy and relationships before hand and test to insure that it really will perform the task you intend it to. Otherwise, it turns into an ugly mess.
Slashdot Mirror
Well, Byte magazine has been around forever. I know it dates back to the early 80s, and probably before that.
There is a backup solution by a company in Seattle called InterVault. It allows you to backup your data to their servers via the Internet. They use encryption to protect your data, so don't lose your password. Their is no backdoor. Check them out at www.intervault.net.
I believe you're refering to Tom Clancy's The Sum Of All Fears.
If they want to give her grief about the napsack, just mention the American's With Disabilites Act. That is still law in the United States, and you can sue them over it.
They had these when I was in high school. You hooked it up to a computer or VCR and placed it on the overhead projector. The problem we always had was that the intensity of the overhead projector always washed out the image. Made it tough to see what the teacher was trying to show us.
Since the FTP site listed had benn slashdotted, you can take a look at here and here for the RFCs.
Back in the good old days, the Internet was rendundant and would route around down nodes. Back in the good old days, the Internet was also run by the National Science Foundation and the Universities. The NSF and the Universities were fairly good at keeping multiple routes up between them. Then along came the commercialization of the Internet. As the Internet became more and more the domain of corporations rather than academics, the philosophy of Intrnet routing changed. No longer did everyone keep links to several different services. Now corporations would sign contracts with each other and charge each other to connect. This resulted in a reduction in the number of links between hosts. Few companies can afford to link to a large number of other routing points, and those that can charge for the privledge of using them. This cycle has continued until the majority of the traffic routes through these network providers. This leads to a situation where, if one of these goes down, all the traffic they had been routing must now be shunted down their 2 or 3 backup links. These links usually have smaller pipes and, therefore, cannot service the enormous amount of traffic being dumped on them. This results in lost packets and unreacheable destinations. How do we fix this problem? That's the big question. The consolidation of network providers has killed the redundancy of the Internet.
At work, the biggest feature of C++ that we insist that everyone use are exceptions. Using exceptions helps us keep code clean and readable and gets rid of multiple nested if statements everytime we have to test for an error condition. The ability to throw an exception and simply catch them all at the bottom makes debugging a lot simpler.
Other features that we use include STL, for the simplicity of creating lists and other data structures, and polymorphism. Since our entire project is an object oriented design, we can't get away from it, and in many cases, it greatly reduces the amount of code we have to write and debug.
That said, however, It is important that you design your object heirarchy and relationships before hand and test to insure that it really will perform the task you intend it to. Otherwise, it turns into an ugly mess.