avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chad Harrington (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AVRO-334) If possible, do not close the socket after every request in sample_ipc_server.py
Date Sat, 16 Jan 2010 00:48:54 GMT

    [ https://issues.apache.org/jira/browse/AVRO-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12801038#action_12801038
] 

Chad Harrington commented on AVRO-334:
--------------------------------------

We also will only use TCP sockets, due to our performance needs.  However, if it is simple
and well-supported to use Avro over our own transport, that is probably best, since we are
equally unlikely to use the stock Avro TCP socket implementation.  We need the performance
and control of our own optimized network stack.  I am guessing there are lots of people like
us, so perhaps the focus should just be on good documentation and testing for running Avro
RPC over arbitrary transports.

> If possible, do not close the socket after every request in sample_ipc_server.py
> --------------------------------------------------------------------------------
>
>                 Key: AVRO-334
>                 URL: https://issues.apache.org/jira/browse/AVRO-334
>             Project: Avro
>          Issue Type: Improvement
>          Components: python
>            Reporter: Jeff Hammerbacher
>
> See http://stackoverflow.com/questions/2066810/does-the-tcpserver-baserequesthandler-in-pythons-socketserver-close-the-socket

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message