[POLL] Upstream/Downstream vs. Inbound/Outbound

[Christian Migowski]

Hi,

I am absolutely for the renaming to Inbound/Outbound*. IMO this is
much more intuitive than the current current Upstream/Downstream*, i
think it will help people new to Netty understand it faster.
It is no problem for me if the API changes because of this.


regards,
christian!



On Mon, May 3, 2010 at 7:51 AM, "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
>