Netty allows Object as usually the user want to write some kind of pojo and then use a *Encoder to convert from it to ByteBuf. So your interface should just expose the pojo as type.
> On 27 Sep 2016, at 02:32, Ming <[email protected]> wrote: > > The write api only needs an object, so I am wondering what *interface* is > assumed for an object to write to a netty channel. I know they can be > ByteBuf, String, FileRegion, etc., but what is the common interface for them > (and many others)? > > -- > You received this message because you are subscribed to the Google Groups > "Netty discussions" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/netty/fed9473d-476f-4c96-84fe-4e6f7a80c4d6%40googlegroups.com > > <https://groups.google.com/d/msgid/netty/fed9473d-476f-4c96-84fe-4e6f7a80c4d6%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "Netty discussions" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/netty/2D7DDF3B-8D49-4EA5-8244-22159B2EE323%40googlemail.com. For more options, visit https://groups.google.com/d/optout.
