I am ready to make the jump to restful webservices

Since you are used to GET and POST operations, the jump is likely to be a small one. Add to that, PUT and DELETE, and you have the complete set of CRUD operations for RESTful webservices.

Aesthetically, RESTful services insist on a strict distinction between the server providing the service, and the client consuming it. However, possibly the most significant point to note is that a RESTful service is generally stateless. The client is expected to manage his own state, independent of the server. A suitable client is therefore one that can resume operation, should the server happen to stop and restart.

Another point to note is that the communication in RESTful webservices consumes much less bandwidth than in traditional webservices. The absence of overheads like SOAP headers, for example, makes RESTful services suitable for portable and mobile devices.