title: REST type API for non web based applications, Is It a good idea?
body: <p>We are developing a middleware SDK, both in C++ and Java to be used as a library/DLL by, for example, game developers, animation software developers, Avatar developers to enhance their products.</p>
  
  <p>Having created a typical API using specific calls for specific functions I am considering simplifying the API by using a REST type API (GET, PUT, POST, DELETE) or CRUD type (CREATE, READ, UPDATE, DELETE) interface.</p>
  
  <p>This would work in a similar way to a client-server type REST API where there are only 4 possible API calls but these can take flexible parameters.</p>
  
  <p>This seems to have the benefit of making the API stable in that new calls are not being added and old calls are not being removed. So a consumer of this API need not worry about having to recompile and change their code to suit any updates to our middleware.</p>
  
  <p>The overhead is that there is an extra layer of redirection in the middleware controller to route API calls and the developer needs to know what parameters are available for each REST call (supplied of course).</p>
  
  <p>I have not so far seen this system used outside of web type client server applications so my question is this: Is this a feasible idea?</p>
  
  <p>I am thinking in terms of its efficiency as well as if for example a game developer would find it easy to use.</p>