The Oasis web standards body is in the early stages of building a specification which will handle asynchrony for web services.
The ASAP (Asynchronous Service Access Protocol) technical committee began regular meetings in early September and the plan is to continue them on a regular basis, according to Keith Swenson, an author of the specification.
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
Swenson is also the chief architect of Fujitsu Software's Interstage, an integration middleware suite.
"ASAP is a standard for long-running web services," Swenson said. He described a long-running web service as one in which a call is made, but the call back does not happen in real time. For instance, when someone orders a book online, it takes a couple days to fill the order and then send the book out.
During that time, ASAP enables the customer to check the status of that order and to cancel it up to a specified point, or ask the web service to call back when the order is fulfilled via any of the transport mechanisms that Soap supports.
To achieve this, ASAP works with another of the evolving standards, Web Services Reliable Messaging, which ensures that the messages sent back and forth are delivered.
The other two authors are Moshe Silverstein of iWay Software and Jeffrey Ricker, who is listed as an individual member.
"The goal is nine months to have a draft that is out for review," Swenson said, adding that although ASAP is new to Oasis, the effort has been under way for six years.
Tom Sullivan writes for InfoWorld