Rafael H. Schloming commented on PROTON-26:

The reason the transport uses input/output rather than read/write is because 
read/write would have exactly the opposite of the usual semantics with respect 
to its arguments. A "read" operation typically populates the passed in array 
with data, whereas the "input" operation is actually providing input in the 
passed in array that is consumed by the transport. Likewise a "write" operation 
usually consumes/copies bytes from the passed in array whereas the "output" 
operation is actually filling the passed in array with output from the 
transport. Reversing the names (input -> write, output -> read) to make the 
semantics similar with respect to the arguments would also be confusing as 
you'd be calling Transport.read in order to produce output to write to the 
network. As it is now it's pretty easy to remember that you read from the 
network to provide input to the transport and when the transport supplies 
output, you write to the network.
> Engine api naming proposal
> --------------------------
>                 Key: PROTON-26
>                 URL: https://issues.apache.org/jira/browse/PROTON-26
>             Project: Qpid Proton
>          Issue Type: Improvement
>          Components: proton-c
>            Reporter: Justin Ross
>         Attachments: engine-naming-01.patch, 
> proton-engine-naming-proposal-2.pdf
> See 
> https://docs.google.com/spreadsheet/ccc?key=0ArGmVtK1EBOMdEw0bkp4OE5UOWpRRkx3RzVoTjliX0E#gid=0

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

Reply via email to