REST
@IMHO:
you do mention the flickr-api. but in my opinion this is not REST like you describe it in your article. flickr has a single service point, and is always using GET methods. (except for uploading fotos, where they use POST) But the power of flickr is that it's so basic to use. just EVERY scripting language / enviroment is able to implement this. as soon as you start to rely on excotic HTTP methods, HTTP-header info, HTTP-Auth, or similiar concepts, people will fail to be able to implement your api.
another problem with rest are its many concepts. there should be a process where at least some stuff gets standardised, or recommended. for example authentication, error handling, xml-formats, use of HTTP-methods. A service could say: "we are using concept A for authentication, concept X for error handling, but we are using our own xml-syntax for responses..." so if you start implementing such an API you could at least use some basic libs for your desired language.
you do mention the flickr-api. but in my opinion this is not REST like you describe it in your article. flickr has a single service point, and is always using GET methods. (except for uploading fotos, where they use POST) But the power of flickr is that it's so basic to use. just EVERY scripting language / enviroment is able to implement this. as soon as you start to rely on excotic HTTP methods, HTTP-header info, HTTP-Auth, or similiar concepts, people will fail to be able to implement your api.
another problem with rest are its many concepts. there should be a process where at least some stuff gets standardised, or recommended. for example authentication, error handling, xml-formats, use of HTTP-methods. A service could say: "we are using concept A for authentication, concept X for error handling, but we are using our own xml-syntax for responses..." so if you start implementing such an API you could at least use some basic libs for your desired language.
matthias - 21. Apr, 09:25
1 comment - add comment - 0 trackbacks
