Published in php|architect
Tuesday, January 6. 2009
Trackbacks
Trackback specific URI for this entry
No Trackbacks
LornaJane
Categories
Pages
Feeds
Links
Quicksearch
Comments
Fri, 03.07.2009 21:14
Using a HTTP Error code doesn’t stop you serving up a custom error page. In fact thats the best way to do it.
People who visit with a web browser will be none the wiser, but anyone that needs to programatically find out what the server responded with can. And if you’re serving up an API err [...]
Fri, 03.07.2009 19:31
I don’t use errors codes at all.
Custom error pages with description what is happened and recommendation what user need to do – it is my way.
Keep in mind not all users can understood error by number and less of them will know what to do.
Fri, 03.07.2009 11:38
shangxiao: my manager is geeky enough that he’d know perfectly well what I was talking about if I used a 4xx code at him :)
Fri, 03.07.2009 06:21
I gather most js libraries will now provide an error handler for 4xx and 5xx, which is quite handy to know whether to display an error dialog. I also use 4xx for when client errors eg when a db constraint fails, I respond with a 4xx and put the error message in the body of the response. For [...]
Thu, 02.07.2009 12:22
Gaetano: I quite like having the version in the URL but that depends a lot on what kind of service you designed as to what makes most sense. I like major.minor as a naming scheme but it is probably overkill as really APIs shouldn’t be changing a lot.
Chris: Whether you support multiple ver [...]
Thu, 02.07.2009 09:21
Bart: yes, we love it – thanks for dropping by!
Caity: It doesn’t seem like 2 years, does it? Looking forward to showing you how much has changed by the time you come again, ooh and I’ll take summer garden photos so you can see the flowers :)
Wed, 01.07.2009 18:58
hey patio looks very smart and i love the garden gate! you can have a very big YAY about being in your house 2 years from me! cant wait to see it all for real! Miss u! Caity x x
Wed, 01.07.2009 15:49
@Gaetano My preference is put version in the URL. This gives you some flexibility on whether to completely branch off and have a new set of API code, or to simply pass the version in as a parameter.
The only scary part about this is that there are now multiple versions of the same API tha [...]
Wed, 01.07.2009 10:08
Interesting post, but more detail would be welcome: – is it a good idea to put version nr. in url, so that new versions of the same webservice can be immediately located? – is using the classic major.minor.revision versioning scheme a good idea or is it overkill? – shall both clients and se [...]