|
Originally posted by silverado
I would like to suggest another reason for the staged release of the patch by Handspring on a carrier-by-carrier basis.
Blazer changes EVERY HTTP request such that it goes though proxy.handspring.com, regardless of whether you use a proxy or not. Every piece of data you see in Blazer has to pass through proxy.handspring.com!
So it's not only a patch readiness issue, it's an infrastructure readiness issue on the part of Handspring. They have to make sure their proxy setup is ready to handle the worldwide demand for GPRS data through Treos. This is not a small undertaking.
I think this is a big factor in this whole saga!
Well.... You make a valid point, but if I were Handspring and I had set up a proxy server, I would have scaled it (actually an array of servers, pointed to a virtual address) to be ready for a world-wide rollout of Treos. So I'm not sure that Handspring would be at fault for the delay considering the nature of the rollout.
If capacity WERE an issue, wouldn't Handspring roll out the technology to the U.S. market first, which has a significantly less developed GSM/GPRS infrastructure (and less demand) than the rest of the world? The U.S. may be a technology leader, but it isn't a wireless leader by any stretch of the imagination. Europe and Asia are heavier users, by far (when it comes to GSM/GPRS). The U.S. is playing "catch-up". So by that observation, if lack of capacity on Handspring's proxy were the reason for the delay in a T-Mobile rollout, why would the patch be released to a GSM/GPRS-savvy market first?
Okay, I'm up to five cents now.
|
|
|