By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,814 Members | 1,050 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,814 IT Pros & Developers. It's quick & easy.

HTTP 1.1 pipelining

P: n/a
can some one guide me how to use HTTP 1.1 pipelining in Python.

Client will generate 3 get requests continuously as shown below and
then read the response for each GET request.

Algorithm
----------
GET(ur1_l)
GET(url_2)
GET(url_3)
readResponse(url_1)
readResponse(url_2)
readResponse(url_3)

i m a python newbie and pls forgive me if this question sounds silly.
thanks in advance for any help.
Jul 18 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
noviceUser wrote:
can some one guide me how to use HTTP 1.1 pipelining in Python.

Client will generate 3 get requests continuously as shown below and
then read the response for each GET request.

Algorithm
----------
GET(ur1_l)
GET(url_2)
GET(url_3)
readResponse(url_1)
readResponse(url_2)
readResponse(url_3)


I don't think this is how HTTP/1.1 pipelining works. It is still a
request-response protocol - the only "pipelining" is in the fact that it
doesn't require a separate connection session for each request-response
pair. That is:

HTTP/1.0:
<establish connection>
GET(url_1)
readResponse(url_1)
<close connection>
<establish connection>
GET(url_2)
readResponse(url_2)
<close connection>
<establish connection>
GET(url_3)
readResponse(url_3)
<close connection>

HTTP/1.1:
<establish connection>
GET(url_1)
readResponse(url_1)
GET(url_2)
readResponse(url_2)
GET(url_3)
readResponse(url_3)
<close connection>

Or maybe you are thinking of establishing parallel connections? In that
case look for some examples using threads and sockets...


--
C isn't that hard: void (*(*f[])())() defines f as an array of
unspecified size, of pointers to functions that return pointers to
functions that return void.
Jul 18 '05 #2

P: n/a
Ivan Voras <ivoras@__geri.cc.fer.hr> schreef:
I don't think this is how HTTP/1.1 pipelining works. It is still a
request-response protocol - the only "pipelining" is in the fact that it
doesn't require a separate connection session for each request-response
pair.


"Pipelining" != "Connection: Keep-Alive"

<http://www.mozilla.org/projects/netlib/http/pipelining-faq.html>

--
JanC

"Be strict when sending and tolerant when receiving."
RFC 1958 - Architectural Principles of the Internet - section 3.9
Jul 18 '05 #3

P: n/a
JanC wrote:
Ivan Voras <ivoras@__geri.cc.fer.hr> schreef:

I don't think this is how HTTP/1.1 pipelining works. It is still a
request-response protocol - the only "pipelining" is in the fact that it
doesn't require a separate connection session for each request-response
pair.

"Pipelining" != "Connection: Keep-Alive"

<http://www.mozilla.org/projects/netlib/http/pipelining-faq.html>


Thank you - it's clearer to me now!

But, isn't this a direct consequence of keep-alive?

Jul 18 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.