RE: Something I don't quite understand, involving HTTPAPI calls (cross-posted to the Midrange and HTTPAPI Lists)

We have a similar setup, and also changed to using a persistent connection, for both eliminating timeouts and performance issues.
Below were the HTTP directives that were needed for persistent connection.

KeepAliveTimeout 86400
MaxKeepAliveRequests 0

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James H. H. Lampert
Sent: Friday, October 05, 2018 8:40 PM
To: Midrange Systems Technical Discussion; HTTPAPI and FTPAPI Projects
Subject: Something I don't quite understand, involving HTTPAPI calls (cross-posted to the Midrange and HTTPAPI Lists)

Ladies and Gentlemen:

I don't quite get this:
In order to do a PUT, I have to do a "http_persist_open" and a
"http_persist_close." And when I use the higher-level calls to do GET
and POST operations, they call those lower-level routines.

And some recent threads on the RPG List tell me that we can stick a
whole series of requests between the "http_persist_open" and the
"http_persist_close."

But everything I've ever read or heard about HTTP tells me that HTTP
doesn't use persistent connections. That "persist" and "HTTP" don't even
belong in the same sentence.

Can somebody explain this seeming oxymoron?

--
JHHL