Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

If asynchronous services are so common, why form a separate technical committee for ASAP?

0
Posted

If asynchronous services are so common, why form a separate technical committee for ASAP?

0

Many standards efforts face an asynchronous challenge or have an asynchronous requirement. Without ASAP, each of these standards efforts would be forced to create their own means of handling an asynchronous exchange in SOAP. There would arise a multitude of systems having a multitude of ways of accomplishing essentially the same task. Is that not what we adopted XML and SOAP to avoid? The objective of ASAP is to provide the minimum functionality necessary to handle an asynchronous exchange in SOAP that other standards efforts can employ in achieving their particular business requirements.

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.