Alarmnummer
Dec 7th, 2005, 02:52 AM
I have a question about the comments about unstable webservice interfaces if you soapify a remote service.
A remote service doesn`t expose the internals of your system. In most cases it will wrap one (or more) local service interfaces. And if you create DTO`s to transfer data, you don`t expose any internal data structures. You have complete control what is exposed.
If you work with a remote service and dto`s, what is wrong with soapifying it?
btw:
I understand why asynchronous communication gives a lot more freedom than synchronous communication. And that is why a document-style webservice is better than a rpc-style webservice. But if we are using an rpc-style webservice, what is wrong with soapifying it?
A remote service doesn`t expose the internals of your system. In most cases it will wrap one (or more) local service interfaces. And if you create DTO`s to transfer data, you don`t expose any internal data structures. You have complete control what is exposed.
If you work with a remote service and dto`s, what is wrong with soapifying it?
btw:
I understand why asynchronous communication gives a lot more freedom than synchronous communication. And that is why a document-style webservice is better than a rpc-style webservice. But if we are using an rpc-style webservice, what is wrong with soapifying it?