The client almost always just listens for success and failure. Both 4xx errors and 500 errors will be caught by the same error callback, so I don't anticipate any problems when changing these error codes around.
Also, it's especially important to keep these error code guidelines in mind when designing and creating the new API endpoints for the modeled data. Hope that helps, Nicolaas On 26 Jul 2012, at 16:07, Chris Tweney wrote: > Yes, please write these up as JIRAs, as they are definitely the wrong > way to express errors. 500s are reserved for programmer error or > misconfiguration/malfunction. > > Another bad practice I've seen is returning 500 but not writing any > error information to the log. If you see that, please JIRA it too. > Every > 500 error should have an error-level log entry so sysadmins can see it > and fix it (or hassle the dev team to fix it). > > I'll let the UI team speak to how the client side handles 500s. I hope > components have not been designed to expect 500 errors in response to > user error! If that's the case then we'll have to tread carefully when > fixing the server side. > > -chris > > On 7/26/12 12:44 AM, Berg, Alan wrote: >> Hi Fellow hard workers, >> >> While looking at the demo version of OAE, I notice occasionally the >> return of 500 status codes from the server side for incorrect inputs >> form the client side. 5xx codes are normally reserved for server side >> errors and 4xx for bad requests. For examples of those look towards >> sending badly formed json requests. Should I jira the one's I find? >> Further, Is there a uniform design practice on the client side to >> deal >> with 5xx errors? >> >> Regards, >> >> Alan >> >> >> Alan Berg >> >> Group Education and Research Services >> Central Computer Services >> University of Amsterdam >> ------------------------------------------------------------------------ >> *From:* [email protected] >> [[email protected]] on behalf of Walsh, Mark >> [[email protected]] >> *Sent:* 26 July 2012 09:15 >> *To:* [email protected] >> *Subject:* Re: [oae-dev] Information on Activities >> >> Hi Angela, >> >> If I understand correctly, I suspect that >> http://localhost:8080/var/search/activity/all.json returns json data >> generated by a all.json template found here [1] >> >> Mark. >> >> [1] all.json activity template >> >> https://github.com/sakaiproject/nakamura/blob/master/bundles/activity/impl/src/main/resources/SLING-INF/content/var/search/activity/all.json >> >> *From:*[email protected] >> [mailto:[email protected]] *On Behalf Of *Qi >> Feng >> *Sent:* Thursday, 26 July 2012 3:55 PM >> *To:* [email protected] >> *Subject:* [oae-dev] Information on Activities >> >> Hi, >> >> I am trying to figure out what kind of information sakai captures >> when >> there is an activity, what kind of activity it captures, and also >> what >> structure it uses to link those events. I can find >> this /var/search/activity/all.json file and open it with my >> browser. I >> cannot find any file called all.json. And that is all I know about >> this >> so far. I would love to know where this all.json file comes from, and >> also if there is any other file I could look at to find information >> on >> activities. Thank you. >> >> Angela Feng >> >> Charles Sturt University <http://www.csu.edu.au/> >> >> | ALBURY-WODONGA | BATHURST | CANBERRA | DUBBO | >> GOULBURN | MELBOURNE | ONTARIO | ORANGE | PORT >> MACQUARIE | SYDNEY | WAGGA WAGGA | >> >> ------------------------------------------------------------------------ >> LEGAL NOTICE >> This email (and any attachment) is confidential and is intended for >> the >> use of the addressee(s) only. If you are not the intended recipient >> of >> this email, you must not copy, distribute, take any action in >> reliance >> on it or disclose it to anyone. Any confidentiality is not waived or >> lost by reason of mistaken delivery. Email should be checked for >> viruses >> and defects before opening. Charles Sturt University (CSU) does not >> accept liability for viruses or any consequence which arise as a >> result >> of this email transmission. Email communications with CSU may be >> subject >> to automated email filtering, which could result in the delay or >> deletion of a legitimate email before it is read at CSU. The views >> expressed in this email are not necessarily those of CSU. >> >> Charles Sturt University in Australia <http://www.csu.edu.au> The >> Chancellery, Panorama Avenue, Bathurst NSW Australia 2795 (ABN: 83 >> 878 >> 708 551; CRICOS Provider Numbers: 00005F (NSW), 01947G (VIC), 02960B >> (ACT)). >> Charles Sturt University in Ontario <http://www.charlessturt.ca/> 860 >> Harrington Court, Burlington Ontario Canada L7N 3N4 Registration: >> www.peqab.ca <http://www.peqab.ca> >> >> Consider the environment before printing this email. >> >> >> _______________________________________________ >> oae-dev mailing list >> [email protected] >> http://collab.sakaiproject.org/mailman/listinfo/oae-dev >> > _______________________________________________ > oae-dev mailing list > [email protected] > http://collab.sakaiproject.org/mailman/listinfo/oae-dev _______________________________________________ oae-dev mailing list [email protected] http://collab.sakaiproject.org/mailman/listinfo/oae-dev
