<HTML><HEAD><META content="text/html; charset=UTF-8" http-equiv="Content-Type"></HEAD><BODY>If you have the reference to the Channel you can get it easily:<BR>
<BR>
ch.getConfig().getBufferFactory()<BR>
<BR>
If you are sure that your protocol will not switch to a different endian, then I think it should be OK to keep your current approach. If you have a reusable handler in your pipeline, then you will prefer my suggested approach.<BR>
<BR>
HTH<BR>
<BR>
Replicator wrote:<BR>
> Can't really keep a reference to the factory, as I have many components (<BR>
> messages, builders, client, server, convenience to/from utility<BR>
> object/methods etc.. ). Feels wrong to pass a factory reference to all of<BR>
> them.<BR>
><BR>
> Thanks.<BR>
><BR>
> --<BR>
> View this message in context: http://netty-forums-and-mailing-lists.685743.n2.nabble.com/Global-Config-Little-Endian-tp6893711p6931256.html<BR>
> Sent from the Netty User Group mailing list archive at Nabble.com.<BR>
> _______________________________________________<BR>
> netty-users mailing list<BR>
> netty-users@lists.jboss.org<BR>
> https://lists.jboss.org/mailman/listinfo/netty-users</BODY></HTML>