Guess what, a whole month after the launch they're still playing with the bandwith manager. They have now limited your number of connections when you first connect... to one thread, and thats bad news for most of us who might start instant messangers, check email, open a few browser windows. The reason? They are trying to close a potential loop hole in thier bandwith manager that might provide full speed within the first minute of connecting to capped users. The result? Degraded service for everybody else who is uncapped and even for those who are capped. Rather than letting you distribute your 8KB/s (while capped) they give you 8KB on one thread (and the same applies to uncapped users, but not with 8B/s). The thing is though, even to people who could abuse this loophole, they'd only get full speed for a very short time (a minute or less) and to capped people who aren't even aware that this loophole exists, they might look like an abuser to a sys admin at WBS if they start downloads or requests as they connect.
You're probably thinking that you can just be more conservative by not opening a ton of internet apps when your first connect. It's not that simple, because in an operating system like windows which might queue a few requests to the windows servers looking for critical updates as soon as an internet connection is detected (within milliseconds of creating the connection) those requests will be queued up one by one and you'll have to wait till every one of them has finished to do anything, check mail, browse, add to that auto updating internet apps, or any app that makes requests to the internet periodically this could seriously hinder your internet experience, so much for "freedom on the internet". If you add in to the equation any background internet operations you may not even be aware of like spybots, trojans etc it can end up being nightmarish because they will hog that one stream and you'll be left wondering why you can't read some news site or check mail.
Right now one thread will go through slowly and all the rest will look like they are being proccessed, so you might see 'Waiting for reply' or 'Waiting for www.somewebsite.com' on threads waiting to be proccessed, but they either take way too long and time out or end up taking several minutes (I counted 12 minutes on one I tested)
I'm not sure if this is temporary or the new way WBS want to piss people off but its definatley not good news for anyone, and obviously don't expect answers from anyone at WBS.
People who know me on this forum know I'm definatley not a WBS basher, I think they have a great product with iBurst, but that is only when they leave it alone, ever since they added thier sloppy bandwith managers thats when people started experiencing problems, and it has to stop. I know alot of WBS bashers might see this as good news, they like any oppurtunity to call WBS incompetent, but WBS... this time you've earned any insult you get. You have a golden goose and you've got it in a choke hold.
I think, wait no I hope, whoever implemented this at WBS, both the brains and the labour saw this as a very temporary solution because they cannot keep it like this, this bandwith manager IS the problem, they have had a month and countless problems with it so why not just buy a professional solution rather than doing patch jobs all the time that DON'T work, I'd love to blame managment but this time I think I need to lay the blame squarly on whatever techie is telling management he is skilled enough to implement feasable solutions. Management just listen to the brains they've hired and the "brains" doesn't know what he/she's doing.
WBS, FIX IT OR DROP IT, it really is that simple
You're probably thinking that you can just be more conservative by not opening a ton of internet apps when your first connect. It's not that simple, because in an operating system like windows which might queue a few requests to the windows servers looking for critical updates as soon as an internet connection is detected (within milliseconds of creating the connection) those requests will be queued up one by one and you'll have to wait till every one of them has finished to do anything, check mail, browse, add to that auto updating internet apps, or any app that makes requests to the internet periodically this could seriously hinder your internet experience, so much for "freedom on the internet". If you add in to the equation any background internet operations you may not even be aware of like spybots, trojans etc it can end up being nightmarish because they will hog that one stream and you'll be left wondering why you can't read some news site or check mail.
Right now one thread will go through slowly and all the rest will look like they are being proccessed, so you might see 'Waiting for reply' or 'Waiting for www.somewebsite.com' on threads waiting to be proccessed, but they either take way too long and time out or end up taking several minutes (I counted 12 minutes on one I tested)
I'm not sure if this is temporary or the new way WBS want to piss people off but its definatley not good news for anyone, and obviously don't expect answers from anyone at WBS.
People who know me on this forum know I'm definatley not a WBS basher, I think they have a great product with iBurst, but that is only when they leave it alone, ever since they added thier sloppy bandwith managers thats when people started experiencing problems, and it has to stop. I know alot of WBS bashers might see this as good news, they like any oppurtunity to call WBS incompetent, but WBS... this time you've earned any insult you get. You have a golden goose and you've got it in a choke hold.
I think, wait no I hope, whoever implemented this at WBS, both the brains and the labour saw this as a very temporary solution because they cannot keep it like this, this bandwith manager IS the problem, they have had a month and countless problems with it so why not just buy a professional solution rather than doing patch jobs all the time that DON'T work, I'd love to blame managment but this time I think I need to lay the blame squarly on whatever techie is telling management he is skilled enough to implement feasable solutions. Management just listen to the brains they've hired and the "brains" doesn't know what he/she's doing.
WBS, FIX IT OR DROP IT, it really is that simple
I am also having severe problems with constant disconnections and web pages timing out tonight. So maybe WBS are still playing..... this is so depressing, at one time I believed you got basically what you paid for... the real world is harsh 
