[POLL] Upstream/Downstream vs. Inbound/Outbound

[Nicholas Hagen]

+1 for renaming. I'd recommend just having the current classes purely  
extend the renamed classes with an empty class body rather than be  
pure copies of each other.  Only require changes to one file.

Nicholas Hagen
Z|NET Development, LLC
www.znetdevelopment.com/blogs
* sent from my iPhone *

On May 3, 2010, at 8:24 AM, Cuper Hector <fcinter at gmail.com> wrote:

> +1 for renaming, inbound is better
>
> On Monday, May 3, 2010, "Trustin Lee (이희승)" <trustin at gmail.com>  
> wrote:
>> Hello community,
>>
>> Some users reported that the upstream/downstream terminology is
>> confusing and hard to remember and inbound/outbound is much better.
>>
>> I agree with them that inbound/outbound fits better, but renaming  
>> types
>> and methods involves backward compatibility issues.  It means the
>> current types and methods whose names contain 'Upstream' or  
>> 'Downstream'
>> will be deprecated and then be removed in the next couple releases.
>>
>> Because it's you who are impacted by the renaming, I'd like to know  
>> if
>> you find the current terminology confusing and would accept the API
>> changes when the changes are made.
>>
>> Thanks for your feed back in advance,
>> Trustin
>>
>> --
>> what we call human nature in actuality is human habit
>> http://gleamynode.net/
>>
>>
>>
>
> _______________________________________________
> netty-users mailing list
> netty-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/netty-users
>