Re: Connection: keep-alive

[Scott Klement <sk@xxxxxxxxxxxxxxxx>]

Hello,

HTTPAPI does allow for persistent connections using the http_persist_xxx 
routines. HTTP_url_post is not persistent. (You should never call 
COMM_xxx routines directly.)

However, these do NOT supply "connection: keep-alive", as that is an 
HTTP 1.0 keyword, and HTTPAPI follows the HTTP 1.1 version of the 
standard. You could force it to send connection: keep-alive via an xproc 
if you need to -- but this is a very strange thing to require. 
Connection: keep-alive was obsolete long before web services became popular.

Note that being persistent isn't necessarily the same as "stateful".  I 
guess the term "stateful" can be interpreted many different ways, and so 
in a sense, persistent HTTP is indeed stateful -- but not from a 
programmer's perspective.  I don't really understand why someone would 
care if a web service is persistent or not.

I can't see why a web service connection would care if the connection is 
persistent.

-SK




On 7/30/2012 11:26 AM, pherrick@xxxxxxxxxx wrote:
> I am using the HTTP_URL_Post.
>
> The requirements of the webservice I am consuming states:
> All HTTP connections must be persistent ('TCP Stateful"), that is , must contain the header
> "Connection: keep-alive" and correctly implement its semantics.
>
> Can HTTP_URL_Post insert the "Connection: keep-alive" into the HTTP header information?
> Or must I do a COMM_Connect, with a http_persist_post?
>
> Thanks for your help
>
>
> -----------------------------------------------------------------------
> This is the FTPAPI mailing list.  To unsubscribe, please go to:
> http://www.scottklement.com/mailman/listinfo/ftpapi
> -----------------------------------------------------------------------
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------