http://codereview.appspot.com/1855044/diff/45001/46006 File java/gadgets/src/main/java/org/apache/shindig/gadgets/uri/UriUtils.java (right):
http://codereview.appspot.com/1855044/diff/45001/46006#newcode144 java/gadgets/src/main/java/org/apache/shindig/gadgets/uri/UriUtils.java:144: resp.sendError(HttpResponse.SC_BAD_GATEWAY); do you intend to merge: http://codereview.appspot.com/1811042/diff/54001/55005?context=50&column_width=100 (setStatus vs. sendError) in this CL as well? That would accommodate the sendError(...) concern to a large degree. Per (http://blogs.atlassian.com/developer/2007/07/responsesenderror_vs_responses.html) [first resource I was able to find on the topic] sendError differs from setStatus only in that sendError sends a preconfigured error page. setStatus presumes you're going to provide the error context itself. So setStatus seems reasonable for most if not all Shindig use cases I've found. http://codereview.appspot.com/1855044/show
