Conceivably, how difficult would it be to share pipelines.
For example, if I have DSL, and there are 3 other users with dial-up access plus one cable modem, it would be possible to create a piece of software to work as a "virutal router" which could split the bandwidth across these various devices. You could even throttle the bandwidth based on need. Two DS1's run at the same speed, however, they have much more bandwidth running in parallel than a single DS1.
On top of this idea, why not create a P2P NOS? Wherein access control is relegated to the various servers online using a smaller version of Directory Services (which, oddly enough, is provided as part of Win2K). Novell Netware does something of this sort with NDS, however the servers must be dedicated, but if you trim-down the server software (and considering today's technology) there's no reason you couldn't embed the server software in the clients.
It is also conceivable that this NOS could be modified to run on the internet as a whole and act as a go-between for these various networks..
Just a thought..
Re:What a union could really achieve...
on
Dial U for Union
·
· Score: 1
It seems to me that a Union's power exists in the theory of safety in numbers. Unions tend to basically overwhelm management to get their ways. This works as much for the good as the bad. On the good side, as long as the union stays on the up-and-up and the employees care about their work, then the company ends up a well-oiled machine (with clear lines of communication between labour and managment). However, if a union leans towards the "bad", then you find that you have a large number of individuals trapped in the horrors of groupthink and hive-mind. You end up with an "elite few" (those being the squeekiest-wheels) who end up steering Labour towards their own ends (read: certain "established" unions that certain truck drivers are required to join).
I myself have had to deal repeatedly with "cookbook coders" being both a full time employee and a consultant. These guys make my life _ver_ difficult. Because they can market better than I do, they end up getting the job (even though I come in with a lower bid). They then botch the job, and the client ends up disdaining contractors, trashing part of my market.
Perhaps a union isn't the answer, but maybe a collaboration amongst various mid-to-high end coders would be slightly more in order. Who knows..
Conceivably, how difficult would it be to share pipelines.
For example, if I have DSL, and there are 3 other users with dial-up access plus one cable modem, it would be possible to create a piece of software to work as a "virutal router" which could split the bandwidth across these various devices. You could even throttle the bandwidth based on need. Two DS1's run at the same speed, however, they have much more bandwidth running in parallel than a single DS1.
On top of this idea, why not create a P2P NOS? Wherein access control is relegated to the various servers online using a smaller version of Directory Services (which, oddly enough, is provided as part of Win2K). Novell Netware does something of this sort with NDS, however the servers must be dedicated, but if you trim-down the server software (and considering today's technology) there's no reason you couldn't embed the server software in the clients.
It is also conceivable that this NOS could be modified to run on the internet as a whole and act as a go-between for these various networks..
Just a thought..
It seems to me that a Union's power exists in the theory of safety in numbers. Unions tend to basically overwhelm management to get their ways. This works as much for the good as the bad. On the good side, as long as the union stays on the up-and-up and the employees care about their work, then the company ends up a well-oiled machine (with clear lines of communication between labour and managment). However, if a union leans towards the "bad", then you find that you have a large number of individuals trapped in the horrors of groupthink and hive-mind. You end up with an "elite few" (those being the squeekiest-wheels) who end up steering Labour towards their own ends (read: certain "established" unions that certain truck drivers are required to join). I myself have had to deal repeatedly with "cookbook coders" being both a full time employee and a consultant. These guys make my life _ver_ difficult. Because they can market better than I do, they end up getting the job (even though I come in with a lower bid). They then botch the job, and the client ends up disdaining contractors, trashing part of my market. Perhaps a union isn't the answer, but maybe a collaboration amongst various mid-to-high end coders would be slightly more in order. Who knows..