Do you produce wonderful ınternet sites? Are you a net developer who crafts fabulous HTML5CSSJS? If that's the case, you must consider HiFi. It can be a brand new web publishing platform that provides you 100% manage more than your HTML mark-up. I assisted design it. Look at it out and inform me what you imagine. "WebKit's Accept header results in world wide 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, 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, suppose there is a resource, 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:"check 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, like so:"check out Jon's work @ but first set your browser to applicationxml"Clearly,
Microsoft Office 2007 Key, this is a step backward compared with something like:"check out Jon's work @ In fact,
Windows 7 Key, the trouble with WebKit's Accept header is not that it is wrong,
Office 2010 Professional, just that it is unexpected. That is, WebKit's behavior is dependent upon a piece of shared state embedded across all WebKit clients and,
Microsoft Office 2010 Product Key, furthermore,
Office Professional Plus 2010, that shared state is different than the shared state embedded across all Firefox clients. None of this sounds RESTful to me.