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

Pretty simple really...

HTTP didn't originally support persistence, every request opened and closed
the TCP/IP connection.

Turned out to be a lot of overhead when you needed multiple resources from
the same server, thus the ability to persist the TCP/IP connection to the
server.

When invoking a web service, if I'm only making a "single" call,
non-persistent connection is fine.

If I'm making multiple calls to the same server, persistent is a better
choice.

Charles



On Fri, Oct 5, 2018 at 6:39 PM James H. H. Lampert <jamesl@xxxxxxxxxxxxxxxxx>
wrote:

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
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD