Regarding Google's Web Accelerator, Rob tells us we were warned. And Rael is summarizing the technology implications. It's clever though. On the one hand some people who think Web architecture matters will consider Google Web Accelerator as a kind of Web lint. Indeed people have been saying this for years.But it's hard to believe this accelerator was shipped without realizing the consequences on web applications. As well as a new found appreciation for Web architecture, including developers who might not have know that the Web had any kind of architecture until today, an expected outcome of the ensuing discussion should be that browser UAs are broken, that HTML forms are broken, and that as a consequence you should upgrade your apps to be Web architecture happy. In fact you should reconsider your entire client stack, because client limitations are driving a lot of the breakage that comes out of the box in server-sided frameworks - workarounds to block the GWA are not a lasting solution - the apps need to be fixed and client churn can drive that. Which suggests XMLHTTPRequest and/or HTML deprecation and/or classic browser deprecation. Now consider this - a well behaved universe of applications will make the Web much more efficient to process for Google, simultaneously lowering their enormous operating costs while making developers everywhere reconsider the makeup of client-side stacks. And you get to say it's architecturally the Right Thing. Really smart play, and really really ambitious....
Previous Topic
