- <@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]>
Stefan
At 11:11 AM 8/3/2005, you wrote:
I have a web service client that is attempting to retrieve a very large soap
envelope from a web service endpoint.
When I hit the endpoint it is responding normally however the response
envelope is truncated.
I determined that the truncated response is 67,604 bytes.
I immediately proceeded to adjust the ItemBuffer size in my config.ini to 4
times the current capacity and restarted the service. No change.
I then reduced the ItemBuffer size to half of the default of 65,535 and
restarted the service, and again no impact.
This has left me to conclude that either one of two events are occurring.
1. there is a separate config for the buffer available to the results of an
<@URL> call that is limited to a size less than 68K and I am unaware of how
to configure this buffer limit.
2. the endpoint is truncating the data (which seems less likely).
Is there anyone that can perhaps shed some light on this issue and provide
direction as to how to resolve it?
Thanks for you cooperation,
Peter Dobbs
Director, Application Development
Football Fanatics Inc.
Moveable Inc.
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
Database WebWorks: Dynamic web sites through database integration
http://www.DatabaseWebWorks.com
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
