Many websites, and even database servers such as Couch DB & Neo4j provide their data over HTTP. Should people implementing client libraries for those APIs use persistent HTTP connections?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Many websites, and even database servers such as Couch DB & Neo4j provide their data over HTTP. Should people implementing client libraries for those APIs use persistent HTTP connections?
Yes. “A significant difference between HTTP/1.1 and earlier versions of HTTP is that persistent connections are the default behavior of any HTTP connection. That is, unless otherwise indicated, the client SHOULD assume that the server will maintain a persistent connection, even after error responses from the server.” See http://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html for more info.