rest - RESTful web service for systems integration understaning -


i am, indeed, new restful services , while feel understand concepts resistant aspects of use in current project.

the project involves provision of form data system. project members insist form data should broken down "resources" there customer , customer addresses etc on form.

so how granular rest api is... form data not complete , actionable until have of form data (and there's little @ that). and, in fact, guess have prepare integrator on service side assemble of these resource bits before can use them because @ present have no persistence them or, specifically, have persistence them need hide data before becomes actionable.

again, @ present point point communications without business case sharing or service composition.

so, i'm of idea 1 service "form" using post acceptable optimization , amount of work cuts pragamatic approach.

what not getting doing hard , expensive way?

if don't need high level definition in need use heavier structure formed , heavy xml dtd, using wsdl, etc. best choice rest, lighter , use http.

here can find better explanation:

wsdl vs rest pros , cons


Comments

Popular posts from this blog

java - Run a .jar on Heroku -

java - Jtable duplicate Rows -

validation - How to pass paramaters like unix into windows batch file -