REST type API for non web based applications, Is It a good idea? -
we developing middleware sdk, both in c++ , java used library/dll by, example, game developers, animation software developers, avatar developers enhance products.
having created typical api using specific calls specific functions considering simplifying api using rest type api (get, put, post, delete) or crud type (create, read, update, delete) interface.
this work in similar way client-server type rest api there 4 possible api calls these can take flexible parameters.
this seems have benefit of making api stable in new calls not being added , old calls not being removed. consumer of api need not worry having recompile , change code suit updates our middleware.
the overhead there layer of redirection in middleware controller route api calls , developer needs know parameters available each rest call (supplied of course).
i have not far seen system used outside of web type client server applications question this: feasible idea?
i thinking in terms of efficiency if example game developer find easy use.
yes, feasible idea. i'm not sure benefits justify costs. rest best applied networked application scenario, oriented around requests , responses. while there definite learning curve advantages uniform interface, advantages can present in well-designed api provides reasonably abstract procedures.
you expressed concern whether game developer find restful api easy use. i'd dubious. i've implemented many restful web services, , helped many developers speed both building them , using them, , conceptual leap required grasp rest can substantial has been steeped in procedural apis years. i'd think game developers in particular connected procedural apis, point attempting adopt different paradigm, whatever benefits, might prove extremely difficult.
Comments
Post a Comment