Pages

02 March 2011

HTML5? Great. Now What About Webserver Error Handling?

I just saw a Google / Arcade Fire video that has been widely viewed (fun stuff!), but this blog post isn't about the video. Rather I was thinking about the apparent status quo with messages and error notification in use for webservers (yes, even vaunted Apache). Sure, there's an API so web developers can intercept the message and put up something more elegant, but the default error processing approaches the unusable. Further, it's often the case that the developer has little control over the cause of such errors. All the more reason for the web server to offer up something sensible. Given the ubiquity of Wikipedia, maybe the user should be directed there, where natural language content curation is held in higher regard than in developer communities. 

No comments:

Post a Comment