Office 2010 Key WebKit Team Admits Error, Downplay

[lettsen04517]

Do you create attractive online resources? Have you been a internet developer who crafts fabulous HTML5CSSJS? In that case, you should try out HiFi. It truly is a new internet publishing platform that provides you 100% command about your HTML mark-up. I assisted construct it. Examine it out and inform me what you imagine. "WebKit's Accept header results in web developers choosing between HTTP incorrectness or a bad user experience. Follow the HTTP spec and your users will get XML dumps as demo'd,Windows 7 Professional Product Key, or do not follow the HTTP spec and roll your own one-off content-negotiation protocol."It is hard to talk about this issue in 140 characters, so here are my thoughts...The naive use of Accept is non-RESTful because it renders external provenance data useless or wrong. For example,Windows 7 Home Basic Activation, suppose there is a resource,Office 2010 Key, that has a XML representation and a HTML representation. Furthermore, assume the XML representation was authored by Jon and the HTML representation was authored by Jake. Now, suppose I tweet something like the following:"investigate out Jon's work @ If you dereference the above URI in Firefox you'll actually be looking at Jake's work. This means I need to send a second piece of state information (almost like a cookie) along with my tweet,Office 2010 Generator, like so:"check out Jon's work @ but first set your browser to applicationxml"Clearly, this is a step backward compared with something like:"investigate out Jon's work @ In fact, the trouble with WebKit's Accept header is not that it is wrong,Office 2010 Standard Serial, just that it is unexpected. That is, WebKit's behavior is dependent upon a piece of shared state embedded across all WebKit clients and, furthermore, that shared state is different than the shared state embedded across all Firefox clients. None of this sounds RESTful to me.