My professional focus has always been on desktop coding, with the web being just a hobby. Any web professionals out there want to comment on how Comcast plans on implementing this so-called "browser hijack?"
My clumsy first guess would be that the spyware-like term "browser hijack" is just hype for non-technicals. Comcast probably just plans on injecting a few lines of HTML into web pages coming back to a user. But wouldn't that mean they'd have to intercept, assemble, and evaluate all of the http response packets going to a particular IP, before letting them through? Sounds expensive and time consuming.
And then wouldn't that also be defeated by anyone who used one of the various web encryption schemes available? Surfing the web this way is slow, but it seems like Comcast is going to throttle part of your connection anyway.
2 comments
[ 3.6 ms ] story [ 12.1 ms ] threadMy clumsy first guess would be that the spyware-like term "browser hijack" is just hype for non-technicals. Comcast probably just plans on injecting a few lines of HTML into web pages coming back to a user. But wouldn't that mean they'd have to intercept, assemble, and evaluate all of the http response packets going to a particular IP, before letting them through? Sounds expensive and time consuming.
And then wouldn't that also be defeated by anyone who used one of the various web encryption schemes available? Surfing the web this way is slow, but it seems like Comcast is going to throttle part of your connection anyway.