I am using RCurl's curlPerform command to send an XML string to an HTTP
server running on the localhost. The command is something like this:
reader <- basicTextGatherer()
curlPerform(url="http://127.0.0.1/",
httpheader=c('Content-Type' = "text/xml; charset=utf-8"),
postfields=toString.XMLNode(xmlRoot(xdoc)),
writefunction=reader$update,
.opts=curlOptions(noproxy="*"))
When sending a short string, the web server responds instantly. However, when
the content-length gets above 1024 bytes, the server takes about 2 seconds to
receive all the content that is being sent to it. I've written the server
myself in Python, so I can see that the delay occurs while the server is
fetching the data from the client, and not at any other point in the response
process. Note that the delay is constant above 1024 bytes; i.e. the delay
doesn't double when the content length goes up to 2048.
Using another client (Excel's MSXML2.ServerXMLHTTP library) yields no delays
regardless of the content length. There are no significant differences as far as
I can tell in the headers that are being sent.
Is curl somehow throttling my connection? I suppose it could be a server-side
issue, but the fact that other clients don't generate the same problems
makes me think it is curl.
Thanks.
This communication is for informational purposes only. It is not
intended as an offer or solicitation for the purchase or sale of
any financial instrument or as an official confirmation of any
transaction. All market prices, data and other information are not
warranted as to completeness or accuracy and are subject to change
without notice. Any comments or statements made herein do not
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries
and affiliates.
This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and any
attachments are believed to be free of any virus or other defect
that might affect any computer system into which it is received and
opened, it is the responsibility of the recipient to ensure that it
is virus free and no responsibility is accepted by JPMorgan Chase &
Co., its subsidiaries and affiliates, as applicable, for any loss
or damage arising in any way from its use. If you received this
transmission in error, please immediately contact the sender and
destroy the material in its entirety, whether in electronic or hard
copy format. Thank you.
Please refer to http://www.jpmorgan.com/pages/disclosures for
disclosures relating to European legal entities.
