[POLL] Upstream/Downstream vs. Inbound/Outbound

[Virat Gohil]

Hi Trustin,

Confusing? Yes. But hardly for more than 5 minutes into the examples. Once I
tried the examples, things were pretty clear from then on.

As far as the re-naming ceremony is concerned, I wouldnt mind
using/migrating to inbound/outbound either. I love this library and the
features that it provides, I am willing to invest a little time to
re-organize my code so that it might be more straightforward to others who
have not tried out the example and directly reading my code.

Just my two cents.

Thanks,

Virat

On Mon, May 3, 2010 at 11:21 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/netty-users/attachments/20100503/b07da4c7/attachment-0001.html