|
Yes, this is exactly what I was looking
for. The maxresultsize was the missing
component. In addition the detailed response is great
for examining the header and I imagine that the wait for result is good for
creating asynchronous services. Now one last question. How to get them to
timeout in the event that the endpoint is not responding in a timely fashion
without timing out the application. p. btw, which version of the manual are you
looking at? I checked my old T2K and the 2002 release
of Witango and these attributes aren't listed. From: Stefan Gonick
[mailto:[EMAIL PROTECTED] Here's the relevant line
from the manual: <@URL LOCATION=location [BASE=base]
[USERAGENT=useragent] [FROM=from] [ENCODING=encoding] [USERNAME=username]
[PASSWORD=password] [POSTARGS=postarglist] [POSTARGARRAY=arrayvariable]
[WAITFORRESULT=true|false] [DETAILEDRESPONSE=true|false]
[MAXRESULTSIZE=size]> Notice the maxresultsize argument. I have a web service client
that is attempting to retrieve a very large soap ________________________________________________________________________TO UNSUBSCRIBE: Go tohttp://www.witango.com/developer/maillist.taf
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf |
- Witango-Talk: Web Service Client Limitation Assistance Roman
- Re: Witango-Talk: Web Service Client Limitation Assista... Stefan Gonick
- RE: Witango-Talk: Web Service Client Limitation Ass... Peter Dobbs
- RE: Witango-Talk: Web Service Client Limitation Ass... Peter Dobbs
- RE: Witango-Talk: Web Service Client Limitation Ass... Stefan Gonick
