This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients Thorben, giampaolo.rodola, pitrou, thorben
Date 2008-09-11.18:32:21
SpamBayes Score 0.00033811296
Marked as misclassified No
Message-id <1221157940.31770.9.camel@fsol>
In-reply-to <3b5d765a0809111050y1432ce41gd87cd8cc58f0db7f@mail.gmail.com>
Content
> now thats interesting:
> adding the line "sock.setsockopt(SOL_TCP, TCP_NODELAY, 1) " decreased
> the delay by half. It still is extremely high but it's a start.

Did you do it on both the client and server sockets?

> Would be interesting to examine the differences between the Perl
> wrapper and the Python wrapper to figure out why Perl "does the right
> thing" in this case and Python doesn't.

Perhaps the Perl wrapper is less thin as the Python one. In any case,
it's by design if the Python socket wrapper doesn't try to be "smart":
the intent is to provide an access to the C API and let people do what
they want with it. Smart things are relegated to higher-level modules or
libraries.
History
Date User Action Args
2008-09-11 18:32:56pitrousetrecipients: + pitrou, giampaolo.rodola, Thorben, thorben
2008-09-11 18:32:22pitroulinkissue3766 messages
2008-09-11 18:32:21pitroucreate