[POLL] Upstream/Downstream vs. Inbound/Outbound

[Enno Shioji]

+1 for not changing.

inbound/outbound is definitely easier to understand, but if somebody
just tells me which is which, it's easy enough to remember.

If there is a phase with all upstream/downstream/inbound/outbound
present it will be more confusing even when *stream will be marked
@depracated..

+1 for changing if *stream can be removed without phased deprecation..




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