FUBAR Spring and Switting nodes
Okay, the weather here has gone berzerk. Again. And for Washington, that's really saying something. (What we casually refer to as "normal" weather is madness.)
How?
Er... Well a photo will explain this better than I can.
No, Everett is not suffering from an epidemic of dandruff, nor is this a crackhead's dream come true. It actually snowed here. SNOW!! IN THE MIDDLE OF APRIL!! The whole damn planet's gone off it's rocker! (Either that or I've finally snapped and gone insane.)
I mean what the hell??!! There was five inches of snow out by Boeing! It was snowing so hard in Lake Stevens that I actually got lost! ( I couldn't read the street signs. Couldn't even hardly see beyond the front of the shop van.)
And on that note, we get our quote of the day from Tom down at the service center: *Walks into the office shaking snow off of his hat* "Eww, I've got global warming all over me."
The snow is gone now, but it is still unseasonably cold here. And it's been hailing on and off all day . Bad.
Next subject: I was sitting in copper cabling class the other day trying to think how I to organize all the internet traffic for She-Tave (My whole "Alliance Space" thing again...) We're talking about a moon of 35 billion people, and hundreds of billions of wired (or wireless) devices generating trillions of data packets an hour. So how do you organize that much data? An ordinary router wouldn't cut it alone. Especially in cases of telemetry devices where they send data important enough to relay to a server, but most of it is redundant.
With that in mind I came up with the idea of a "Switting Node" (Switting being a combination of sorting and writing).
The idea here is a router that not only sorts traffic, and kills unnecissary stuff, but also writes a bit of it's own.
I'm imagining a device like this would communicate constantly with every other switting node in the vicinity (or maybe just a declared master node) to figure out which devices are causing the most replicant traffic, and if anyone else has identical traffic. It then forwards a small binary packet to the server telling it which other switting node to reference for that data, and kills the replicant packets.
Granted a network would have to be massive for a Switting node to make a difference, but on a truly enormous scale it could probably help lower traffic on the network, and save enough bandwidth to make it worthwhile.
Anyhow. I need sleep. I'm tired and my eyes are bloodshot.
~Talen
How?
Er... Well a photo will explain this better than I can.
No, Everett is not suffering from an epidemic of dandruff, nor is this a crackhead's dream come true. It actually snowed here. SNOW!! IN THE MIDDLE OF APRIL!! The whole damn planet's gone off it's rocker! (Either that or I've finally snapped and gone insane.)
I mean what the hell??!! There was five inches of snow out by Boeing! It was snowing so hard in Lake Stevens that I actually got lost! ( I couldn't read the street signs. Couldn't even hardly see beyond the front of the shop van.)
And on that note, we get our quote of the day from Tom down at the service center: *Walks into the office shaking snow off of his hat* "Eww, I've got global warming all over me."
The snow is gone now, but it is still unseasonably cold here. And it's been hailing on and off all day . Bad.
Next subject: I was sitting in copper cabling class the other day trying to think how I to organize all the internet traffic for She-Tave (My whole "Alliance Space" thing again...) We're talking about a moon of 35 billion people, and hundreds of billions of wired (or wireless) devices generating trillions of data packets an hour. So how do you organize that much data? An ordinary router wouldn't cut it alone. Especially in cases of telemetry devices where they send data important enough to relay to a server, but most of it is redundant.
With that in mind I came up with the idea of a "Switting Node" (Switting being a combination of sorting and writing).
The idea here is a router that not only sorts traffic, and kills unnecissary stuff, but also writes a bit of it's own.
I'm imagining a device like this would communicate constantly with every other switting node in the vicinity (or maybe just a declared master node) to figure out which devices are causing the most replicant traffic, and if anyone else has identical traffic. It then forwards a small binary packet to the server telling it which other switting node to reference for that data, and kills the replicant packets.
Granted a network would have to be massive for a Switting node to make a difference, but on a truly enormous scale it could probably help lower traffic on the network, and save enough bandwidth to make it worthwhile.
Anyhow. I need sleep. I'm tired and my eyes are bloodshot.
~Talen