lettsen04517
03-22-2011, 11:10 AM
Do you build gorgeous sites? Have you been a net developer who crafts spectacular HTML5CSSJS? If so,Office 2010 Standard (http://www.office2010-key.org/), you might want to look at HiFi. It truly is a brand new website publishing platform that offers you 100% manage around your HTML mark-up. I served formulate it. Verify it out and tell me what you suppose. "WebKit's Accept header results in internet developers choosing between HTTP incorrectness or a bad user experience. Follow the HTTP spec and your users will get XML dumps as demo'd,Office Pro Plus 2010 (http://www.office2010-key.us/), 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,Windows 7 Enterprise (http://www.microsoftwindows7key.net/), 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:"verify 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:"examine out Jon's work @ but first set your browser to applicationxml"Clearly, this is a step backward compared with something like:"verify out Jon's work @ In fact, the trouble with WebKit's Accept header is not that it is wrong, just that it is unexpected. That is,Office Enterprise 2007 Key (http://www.office2007-key.org/), WebKit's behavior is dependent upon a piece of shared state embedded across all WebKit clients and, furthermore,Windows 7 Enterprise Key (http://www.key-windows-7.co.uk/), that shared state is different than the shared state embedded across all Firefox clients. None of this sounds RESTful to me.