Re: IBM i in the cloud (was social media)

On 11/21/2010 5:41 PM, Henrik RÃtzou wrote:

What simple REST services do is to provide the client the right to chain,
read, write, update and delete in the database - do you really want to
package that into a complex SOAP structure with WDLS an so ? How many hours
of click click click in EGL do you think it will take you to make lets say
6000 SOAP services ?

I don't need 6000 services. In fact, I don't need anything nearly as cumbersome as that. I need one or two services per object - one for list operations and another for CRUD operations. A typical application might require a couple of dozen services.

And you keep gliding between REST and SOAP, but I find them to be very different. I use SOAP for external transactions which require authorization and authentication on a transaction-by-transaction basis and REST for inter-tier communications where the authorization is done at the application level.

I don't think you and I agree on what a service architecture is supposed to be.

Seriously. 6000 services? Dude.

Joe