[POLL] Upstream/Downstream vs. Inbound/Outbound

[liwei]

+2 for no renaming.
I don't think upstream and downstream is confusing, cause in network layered
architecture graph, people always put the application layer in the above,
and put the transport layer in the below, just think about the TCP/IP model
and the OSI model.

On Tue, May 4, 2010 at 3:40 AM, Rafael Marins <rafael.marins at neociclo.com>wrote:

> +1 renaming
>
> Cheers,
> --
> Rafael Marins
>
>
>
>
> On May 3, 2010, at 2:51 AM, Trustin Lee (이희승) 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
>
>
>
> _______________________________________________
> netty-users mailing list
> netty-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/netty-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/netty-users/attachments/20100513/b42dcfc1/attachment-0001.html