You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Colin Patrick McCabe (JIRA)" <ji...@apache.org> on 2013/01/03 12:16:12 UTC
[jira] [Created] (HDFS-4353) Encapsulate connections to peers in
Peer and PeerServer classes
Colin Patrick McCabe created HDFS-4353:
------------------------------------------
Summary: Encapsulate connections to peers in Peer and PeerServer classes
Key: HDFS-4353
URL: https://issues.apache.org/jira/browse/HDFS-4353
Project: Hadoop HDFS
Issue Type: Sub-task
Components: datanode, hdfs-client
Affects Versions: 2.0.3-alpha
Reporter: Colin Patrick McCabe
Assignee: Colin Patrick McCabe
Attachments: 02-cumulative.patch
Encapsulate connections to peers into the {{Peer}} and {{PeerServer}} classes. Since many Java classes may be involved with these connections, it makes sense to create a container for them. For example, a connection to a peer may have an input stream, output stream, readablebytechannel, encrypted output stream, and encrypted input stream associated with it.
This makes us less dependent on the {{NetUtils}} methods which use {{instanceof}} to manipulate socket and stream states based on the runtime type. it also paves the way to introduce UNIX domain sockets which don't inherit from {{java.net.Socket}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] [Created] (HDFS-4353) Encapsulate connections to peers in Peer and PeerServer classes
Posted by Vinod Kumar Vavilapalli <vi...@hortonworks.com>.
Send an email to hdfs-dev-unsubscribe@hadoop.apache.org .
Thanks,
+Vinod
On Jan 3, 2013, at 3:38 AM, gschen.fudan wrote:
> hi,
>
> how could I unsubscribe from this mailing list?
>
>
> thank you very much.
>
> justin
>
> 于 2013/1/3 19:16, Colin Patrick McCabe (JIRA) 写道:
>> Colin Patrick McCabe created HDFS-4353:
>> ------------------------------------------
>>
>> Summary: Encapsulate connections to peers in Peer and PeerServer classes
>> Key: HDFS-4353
>> URL: https://issues.apache.org/jira/browse/HDFS-4353
>> Project: Hadoop HDFS
>> Issue Type: Sub-task
>> Components: datanode, hdfs-client
>> Affects Versions: 2.0.3-alpha
>> Reporter: Colin Patrick McCabe
>> Assignee: Colin Patrick McCabe
>> Attachments: 02-cumulative.patch
>>
>> Encapsulate connections to peers into the {{Peer}} and {{PeerServer}} classes. Since many Java classes may be involved with these connections, it makes sense to create a container for them. For example, a connection to a peer may have an input stream, output stream, readablebytechannel, encrypted output stream, and encrypted input stream associated with it.
>>
>> This makes us less dependent on the {{NetUtils}} methods which use {{instanceof}} to manipulate socket and stream states based on the runtime type. it also paves the way to introduce UNIX domain sockets which don't inherit from {{java.net.Socket}}.
>>
>> --
>> This message is automatically generated by JIRA.
>> If you think it was sent incorrectly, please contact your JIRA administrators
>> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
Re: [jira] [Created] (HDFS-4353) Encapsulate connections to peers
in Peer and PeerServer classes
Posted by "gschen.fudan" <10...@fudan.edu.cn>.
hi,
how could I unsubscribe from this mailing list?
thank you very much.
justin
于 2013/1/3 19:16, Colin Patrick McCabe (JIRA) 写道:
> Colin Patrick McCabe created HDFS-4353:
> ------------------------------------------
>
> Summary: Encapsulate connections to peers in Peer and PeerServer classes
> Key: HDFS-4353
> URL: https://issues.apache.org/jira/browse/HDFS-4353
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: datanode, hdfs-client
> Affects Versions: 2.0.3-alpha
> Reporter: Colin Patrick McCabe
> Assignee: Colin Patrick McCabe
> Attachments: 02-cumulative.patch
>
> Encapsulate connections to peers into the {{Peer}} and {{PeerServer}} classes. Since many Java classes may be involved with these connections, it makes sense to create a container for them. For example, a connection to a peer may have an input stream, output stream, readablebytechannel, encrypted output stream, and encrypted input stream associated with it.
>
> This makes us less dependent on the {{NetUtils}} methods which use {{instanceof}} to manipulate socket and stream states based on the runtime type. it also paves the way to introduce UNIX domain sockets which don't inherit from {{java.net.Socket}}.
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA administrators
> For more information on JIRA, see: http://www.atlassian.com/software/jira