Hi Anish,
Anish Karmarkar wrote:
4A0C4348.6090203@oracle.com" type="cite">Simon
Nash wrote:
Anish,
As currently written, the conformance section requires that
implementations claiming support for the SCA Web Services
Callback Protocol MUST support both the "regular" flavor
defined in section 5 and the WS-MC flavor defined in section
5.1. I thought the intention was to give these two flavors
equal status and allow implementations to support either or
both of them.
I had thought otherwise. I.e., a runtime is required to support both. A
particular service/composite gets to choose whether it wants to use
polling or host a listener. I don't feel strongly about this, but we
should discuss as to what we would like.
I side with Simon here. In the scenario where I support callbacks, I
can have lots of reasons for not supporting callbacks via a polling
mechanism. To wit:
- Security
- Latency
- Bandwidth consumption
There are other, far better ways to send messages asynchronously (JMS,
SMTP, XMPP), and mandating that any implementation that supports the
direct callback mechanism must also support the polling callback flies
in the face of this simple technical observation. Why would we want to
mandate the use of an inferior approach?
-Eric.
|