I've used clone() with a thread wrapper for concurrent calls as Jeff
describes, and it works fairly well. That said, an async method would
be strongly preferred :).
On Wed, Dec 9, 2009 at 10:50 AM, Bruce Edge <bruce.edge(a)gmail.com> wrote:
I'm also interested in support for SOAP async operations.
Specifically for
interacting with CXF.
So, I'm throwing my vote in for that feature.
Keep up the great work.
-Bruce
On Wed, Dec 9, 2009 at 6:03 AM, Jeff Ortel <jortel(a)redhat.com> wrote:
>
> Hey Joe,
>
> Currently suds provides very little support for concurrent or asynchronous
> soap method invocation. The (1) things it does provide is a Client.clone()
> method for creating light-weight copies of the client to be used in
> different threads.
>
> For now I'd suggest you wrap the cloned clients in your own threading
> wrapper that also provides the callbacks.
>
> That said, I would be to add 1st class support for this (perhaps in the
> next release).
>
> Regards,
>
> Jeff
>
> On 12/07/2009 11:04 AM, Sarbak, Joseph wrote:
>>
>> Hello,
>>
>> Does the suds api provide a way for clients to pass a callback to handle
>> return values from an asynchronous soap method call? If not, then can
>> someone suggest a way to hack asynchronous calls?
>>
>> Thank you.
>> Joe Sarbak
>>
>> ________________________________________
>>
>> This E-Mail (including any attachments) may contain privileged or
>> confidential information. It is intended only for the addressee(s)
>> indicated above.
>>
>> The sender does not waive any of its rights, privileges or other
>> protections respecting this information.
>>
>> Any distribution, copying or other use of this E-Mail or the information
>> it contains, by other than an intended recipient, is not sanctioned and is
>> prohibited.
>>
>> If you received this E-Mail in error, please delete it and advise the
>> sender (by return E-Mail or otherwise) immediately.
>>
>> This E-Mail (including any attachments) has been scanned for viruses.
>>
>> It is believed to be free of any virus or other defect that might affect
>> any computer system into which it is received and opened.
>>
>> However, it is the responsibility of the recipient to ensure that it is
>> virus free.
>>
>> The sender accepts no responsibility for any loss or damage arising in
>> any way from its use.
>>
>> E-Mail received by or sent from RBC Capital Markets is subject to review
>> by Supervisory personnel.
>>
>> Such communications are retained and may be produced to regulatory
>> authorities or others with legal rights to the information.
>>
>> IRS CIRCULAR 230 NOTICE: TO COMPLY WITH U.S. TREASURY REGULATIONS, WE
>> ADVISE YOU THAT ANY U.S. FEDERAL TAX ADVISE INCLUDED IN THIS COMMUNICATION
>> IS NOT INTENDED OR WRITTEN TO BE USED, AND CANNOT BE USED, TO AVOID ANY U.S.
>> FEDERAL TAX PENALTIES OR TO PROMOTE, MARKET, OR RECOMMEND TO ANOTHER PARTY
>> ANY TRANSACTION OR MATTER.
>>
>>
>>
>> _______________________________________________
>> fedora-suds-list mailing list
>> fedora-suds-list(a)redhat.com
>>
https://www.redhat.com/mailman/listinfo/fedora-suds-list
>
>
> _______________________________________________
> fedora-suds-list mailing list
> fedora-suds-list(a)redhat.com
>
https://www.redhat.com/mailman/listinfo/fedora-suds-list
_______________________________________________
fedora-suds-list mailing list
fedora-suds-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-suds-list