[
https://issues.apache.org/jira/browse/AVRO-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12800878#action_12800878
]
Doug Cutting commented on AVRO-334:
-----------------------------------
As I think about it more, I'd prefer we focus on http rather than sockets. I'd
like to minimise the number of transports that an Avro implementation must
support. Ideally we'd have just one. It's clear that HTTP is a useful,
standard transport, but Y! does not believe it's the appropriate basis for
secure RPC in Hadoop. So we'll probably support one other Avro-specific
transport. My current guess is that this will be SASL over TCP, so much like
our current socket transports, but not identical. I'd rather not support a
third, TCP w/o SASL, since that just multiplies the implementation effort and
potential mismatches. So for now, until the details of the SASL over TCP
transport are fleshed out, HTTP is probably a better first transport for
implementations.
> 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.
