Upstream/Downstream confusing--Inbound/Outbound better!

["Trustin Lee (이희승)"]

You are right.  I was confused briefly.  Actually, there was a related
discussion before:

    http://markmail.org/message/qhf2hl7ums5cxnsv

Personally, I'm fine with the current upstream / downstream terminology,
but I'd like to know what people think about inbound / outbound
terminology and rename the types and methods if there is consensus.

Let me begin a poll soon.

Tuure Laurinolli wrote:
> What do you mean reversed? Surely data sent to a client from a peer 
> (i.e. inbound data) is handled in ChannelUpstreamHandler, just like data 
> sent from a peer to a server?
> 
> On 2010-03-25 05:55, "Trustin Lee (이희승)" wrote:
>> It's only when you write a server.  When writing a client, it's reversed. :)
>>
>> falconair wrote:
>>> I noticed that as i use the API, I keep having to remember exactly what
>>> upstream and downstream refer to.  Incidentally, the API docs for
>>> ChannelPipeline describe them as INBOUND data and OUTBOUND data.  This looks
>>> much more natural to me.
>>
>>
>> _______________________________________________
>> netty-users mailing list
>> netty-users at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/netty-users
> 
> _______________________________________________
> netty-users mailing list
> netty-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/netty-users

-- 
what we call human nature in actuality is human habit
http://gleamynode.net/


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 260 bytes
Desc: OpenPGP digital signature
Url : http://lists.jboss.org/pipermail/netty-users/attachments/20100503/27ac3bfd/attachment-0001.bin