> You are correct that the SOAP Binding is currently only synchronous. The
> idea was to support a simple, mandatory to implement scheme, to insure basic
> interoperability. Frankly no one mentioned this as a requirement. Our main
> focus has been online environments in which an answer is needed immediately.
Thank you for your reply. I have been able to understand the
specification more deeply.
Now I'm developing SAML-aware access management system.
It affects architecture design whether SOAP Binding supports
asynchronous response or not, so I ask saml-dev ml about this question.
> The SSTC (SAML) is preparing to begin work on new features very soon. It
> would be good to submit this requirement. Do you have a usecase in mind that
> would clarify how this capability would be used?
I think the back-office transaction use-case, which has been already
proposed, will require an asynchronous,reliable transport mechanism like
ebXML for sending arbitrary e-business transaction documents(ex.
invoices, bill...) as assertions. So I think I have to consider an
asynchronous transport in designing the architecture.
Is it my misunderstanding?
Best Regards,
----------------------------------------------
NTT Data Corporation
Yuji Sakata
Tel: +81-3-3523-8081
E-Mail:
----------------------------------------------
