Over the years there have been different methods of for communicating between heterogeneous systems. \u00a0Each of these methods have to deal binary messaging. \u00a0Some of the different protocols that have been used are as follows.<\/p>\n
These protocols are of varying complexity and some of the descriptions that have been used to describe them are complexity, rigid, complex, heavyweight\u00a0and complicated.<\/p>\n
Each time the technology wheel turns a new protocol is created with the goal to create something that is powerful and lightweight.<\/p>\n
Restful web services is an attempt at providing a lightweight but scaleable communications protocol that can be called from any platform. \u00a0It uses a simple URL instead of creating and passing complicated XML structures<\/p>\n
This should\u00a0be a very simple way of submitting information or retrieving data. \u00a0A colleague once recommended that I create my own web services for processing my weekly expenses while I was on the road.<\/p>\n
At that time, it seemed like overkill to create such a solution in order to process anywhere from 5 to 10 expense items per week.<\/p>\n
I did have the interest\u00a0in the project but ended up focusing my efforts on dabbling in the hardware arena by creating a LED cube<\/a>. \u00a0Eventually, my interest has come back to web services.<\/p>\n Of course as what often happens is that you cannot start something without doing something else first – in this case all the prerequisite software.<\/p>\n My laptop is a bit of a mess so I choose to create a small virtual machine and do all of my work there. \u00a0This is actually a extremely interesting use of those extra cpu cycles and could become common for even basic computer users in the future. \u00a0I hope to go into that at a later point.<\/p>\n For working with restful web services I needed to install the following.<\/p>\n Once everything was setup, I did get a chance to create both a a server and a client. \u00a0I will not actually setup my own restful server setup \u00a0for remotely doing my expenses but I may end up using the technology for something else in the future.<\/p>\n The next few blog<\/a> entries create a few simple examples to put the technology through its paces.<\/p>\n http:\/\/blog.smartbear.com\/apis\/understanding-soap-and-rest-basics\/<\/a><\/p>\n","protected":false},"excerpt":{"rendered":" Over the years there have been different methods of for communicating between heterogeneous systems. \u00a0Each of these methods have to deal binary messaging. \u00a0Some of the different protocols that have been used are as follows. Remote procedure calls (RPC) Distributed … Continue reading \n
Difference between Soap and Rest protocols.<\/h2>\n