Overall, I split application integration (AI) methods into two groups, passive and active. Passive is typified by bulk data transfers on a regular schedule (e.g. nightly, weekly). On the other hand, with active AI methods some action is required to initiate the interaction, such as calling an API function. In my experience, passive AI methods are by far more common, and they have served us well compared to the darks days when data was re-keyed to get it into multiple systems. The shortcomings of passive AI include having out-of-date data and no ability to access the logic of other applications. Active AI, to the contrary, allows access to "live" up-to-date data and to logic accessed through an API.
IMHO, SOAP eases AI by providing a low cost, programming language independent means for implementing active AI through an API. While it is true that logic is not itself moved over the wire, a well designed API can give you access to the logic you need, although at the expense of always having to access it remotely. There are times when I rather prefer the security inherent in this, as I don't have to execute "foreign" code on my own systems. Scott Nichol ----- Original Message ----- From: "soap vamsi" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, August 27, 2002 8:55 AM Subject: Role of soap in application integration hi all, SOAP implementations send and return objects as beans to/from services.In the RPC scenario,what good will a bean deplete of the application logic be if i want to integrate my application with a soap service. If my concern is valid how does soap ease application integration? thanx in advance vamsi -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
