[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Set the time out limited
Scott
That was very useful information. So this is our API that I believe we
are using:
http_url_post_xml( ServiceURL
: %addr(SOAP) + 2
: %len(SOAP)
: %paddr(StartOfElement)
: %paddr(EndOfElement)
: *NULL
: HTTP_TIMEOUT
: HTTP_USERAGENT
: 'text/xml'
: 'WebServiceControl');
I see the "timeout" parameter is HTTP_TIMEOUT, I assume it to be global
variable, would you maybe know how I could go about finding where it is
declared and maybe how to set it? I suspect it to be a default variable
with the HTTP API, am I wrong?
Also we using a windows web services server. I would to know, is it
possible for a web services server to send a byte back every 30
seconds? and will that keep the connect alive?
Enjoy
Devlyn
From: Scott Klement <sk@xxxxxxxxxxxxxxxx>
To: HTTPAPI and FTPAPI Projects <ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
Date: 2012/11/19 05:13 PM
Subject: Re: Set the time out limmited
Sent by: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
__________________________________________________________________
Devlyn,
"Timeout" is one of the parameters to the APIs. You can set it to any
value you like. For example:
rc = http_get( myURL: myStmf: 120 );
In the above example, I've set the timeout to 120 seconds. All of
the
HTTP APIs that perform network access have a timeout parameter. Check
the parameter lists in HTTPAPI_H for the API you're calling.
Also... the way the timeout works: It's NOT measuring the total
run-time of the API. Instead, it's measuring the "lull" time on the
connection. So.. suppose you are downloading a very large file with
HTTPAPI, and it will take 1 hour to download. A timeout of 60 seconds
is no problem, here... it does not matter that the file download
takes
an entire hour, because the "60 seconds" is not measuring the download
time. AS long as you receive at least 1 byte every 60 seconds,
HTTPAPI
will be happy. However, if it should occur that HTTPAPI receives
nothing for 60 seconds (not even a single byte) then it will close the
connection and report a timeout error.
But, yeah, you can set it to a higher number... just change the timeout
parameter. The only "thing to watch out for" is that dead connections
will take longer to time out.
-SK
On 11/19/2012 4:10 AM, vanderWalt.Devlyn@xxxxxxxxxxxxxx wrote:
> Hi All
> We are starting to notice when a few of our processes that take
longer
> than a minute, we start getting time out errors. Is there a way
to
> increase the time out limit? And in doing so what must one look
out
> for?
> Enjoy
> Devlyn
>
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
[1]http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
__________________________________________________________________
This e-mail is subject to the Columbus Stainless [Pty] Ltd Email Legal
Notices available at:
[2]http://www.columbus.co.za/EmailLegalNotice.htm.
__________________________________________________________________
This e-mail message has been scanned for Viruses and Content and
cleared by MailMarshal
__________________________________________________________________
References
1. http://www.scottklement.com/mailman/listinfo/ftpapi
2. http://www.columbus.co.za/EmailLegalNotice.htm
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------