|
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,hours
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
of click click click in EGL do you think it will take you to make letssay
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
--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.